Technical impact
A flaw in Apache Wicket’s authentication module means that when a user who has already signed into a session attempts to authenticate again—such as during a step‑up verification, account switch, or repeated submission of a sign‑in form—the framework will not regenerate the underlying session identifier. The session’s ID is only regenerated on the very first sign‑in. Because the sign‑in method returns true regardless of whether a renewal occurs, applications have no indication that the session ID has not been refreshed, allowing an attacker who can pre‑place a session identifier in a victim’s browser to force the victim to use that attacker‑controlled session and thereby hijack the session.
Affected Systems
The vulnerability affects Apache Wicket releases from 8.18.0 through 8.19.0, from 9.23.0 through 9.24.0, and from 10.9.0 through 10.11.0. Applications that use AuthenticatedWebSession with the default UsernamePasswordPanel and do not implement custom session‑ID renewal logic are vulnerable.
Risk and Exploitability
The CVSS score of 7.2 indicates a high‑severity vulnerability, but exploitation requires the attacker to supply a chosen session identifier in the victim’s browser. This can be achieved only if the attacker controls a host within the same registrable domain or if the servlet container forwards the session ID via the URL, which is not the default configuration. The EPSS score is not publicly available and the vulnerability is not listed in CISA’s KEV catalog, implying that there is currently no known widespread exploitation. Nonetheless, the lack of session renewal on re‑authentication could allow a remote attacker with domain or URL‑based session access to hijack an authenticated session, compromising both confidentiality and integrity of user data.