Technical impact
Incorrect ordering of security checks in the ResourceIsolationRequestCycleListener causes the listener to instantiate a page before evaluating resource isolation policies. Instantiation triggers the configured IAuthorizationStrategy, which can throw a RestartResponseAtInterceptPageException for unauthenticated visitors. Because the exception is thrown inside the listener, it replaces the request handler before the isolation policies run, allowing a cross‑origin request to be recorded but not blocked. The exception stores the original request URL, including its query string, so that when the visitor signs in the framework automatically redirects to that stored URL. The redirect is considered same‑origin, so the isolation policies are bypassed and the listener runs in the authenticated session, replaying the original request’s query parameters into a form. This effectively lets an attacker craft a link on a malicious site that, after the victim logs in, causes the victim’s browser to submit a form with data chosen by the attacker.
Affected Systems
The flaw affects Apache Wicket versions 9.1.0 through 9.24.0 and 10.0.0 through 10.11.0 in apps that opt‑in to ResourceIsolationRequestCycleListener and use the common pattern of refusing unauthorized access with RestartResponseAtInterceptPageException followed by continueToOriginalDestination. Applications that never register the listener, or that already use a different exception such as RestartResponseException, are not affected. Users on Wicket 8.x and 9.0.0 are also unaffected because the relevant policy was introduced in 9.1.0.
Risk and Exploitability
The CVSS score of 2.1 labels this a low‑severity issue, and the EPSS score is not available, indicating limited evidence of exploitation. Attackers could exploit this by hosting a malicious page that links to the vulnerable target; when a user clicks the link while not authenticated, the application redirects them to the login page and, after successful authentication, automatically visits the original URL, submitting the attacker‑chosen query parameters. This requires the victim to be authenticated or to log in, making social engineering or phishing a likely vector. The vulnerability is listed in no KEV catalog, and no public exploit has been reported. Patching to 9.25.0 or 10.12.0 eliminates the flaw and restores proper policy enforcement before page instantiation.