Technical impact
The flaw occurs in Apache Wicket's AjaxNewWindowNotifyingBehavior when it stores a client‑supplied window.name in the page state. During rendering, the stored name is embedded unescaped into a JavaScript string literal and written directly to the page. An attacker can supply a window name containing script that terminates the string literal and injects code, leading to cross‑site scripting that runs in the application's origin. The impact is that an attacker can run arbitrary JavaScript in a victim’s browser, which may compromise cookies, session data, or perform other malicious actions.
Affected Systems
Affected products are Apache Wicket 8.x versions 8.0.0 through 8.19.0, 9.x versions 9.0.0 through 9.24.0, and 10.x versions 10.0.0 through 10.11.0. Only applications that explicitly add AjaxNewWindowNotifyingBehavior are vulnerable; the framework itself does not install it.
Risk and Exploitability
The CVSS score of 7.6 indicates high severity. The EPSS is not available, and the vulnerability is not listed in the CISA KEV catalog. The attack vector relies on client input through the browser’s window name, so any user who opens a malicious link in a browser running the affected application could trigger the exploit. Mitigation requires the vendor’s patch or appropriate input validation. No public exploit data is currently available, but the high severity warrants prompt action.