CVE-2026-82956

Apache Wicket: XSS in AjaxNewWindowNotifyingBehavior via the client-supplied window name

Published Nov 1, 2026 CVSS 4.0 · 7.6 High EPSS < 1% KEV · Not listed
Description
Improper neutralization of input during web page generation in Apache Wicket.

org.apache.wicket.ajax.AjaxNewWindowNotifyingBehavior notices that a page instance has been opened in a second browser window or tab. It asks the browser for the value of window.name, which reaches the server as the request parameter windowName, and remembers what the browser reported in a field of the behaviour. That field is part of the page's serialized state, so the remembered value stays in the page store for as long as the page instance does.

On every later render of that page instance the behaviour builds the precondition of its Ajax call by substituting the remembered value into a single-quoted JavaScript string literal, and Wicket writes that precondition into the page as raw JavaScript, because the precondition of an Ajax call listener is script supplied by the caller and is emitted without quoting or escaping. Nothing on that path escapes the value. The window name is client-supplied and Wicket applies no validation to it, so a remembered name containing a single quote ends the literal and the rest of it runs as script in the application's origin, every time that page instance is rendered.

An application is affected only where it has explicitly added AjaxNewWindowNotifyingBehavior to a component. No part of the framework installs the behaviour, so an application that does not use it is not affected. The name the behaviour generates for itself, when the browser reports no name at all, is a random UUID and is not client-supplied.

This issue affects Apache Wicket: from 8.0.0 through 8.19.0, from 9.0.0 through 9.24.0, from 10.0.0 through 10.11.0.

Users are recommended to upgrade to version 8.20.0, 9.25.0 or 10.12.0, which fix the issue.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Wicket to version 8.20.0, 9.25.0, or 10.12.0 (or newer) to apply the vendor fix.
  • If an upgrade is not immediately possible, remove or disable AjaxNewWindowNotifyingBehavior from the application, or refactor to use a validated window name.
  • Implement input validation or output encoding for any user‑supplied window.name value before storing or rendering it, or configure the framework to escape the value.

Generated by OpenCVE AI on November 1, 2026 at 23:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Apache
Apache wicket
Vendors & Products Apache
Apache wicket
Type Values Removed Values Added
Description Improper neutralization of input during web page generation in Apache Wicket. org.apache.wicket.ajax.AjaxNewWindowNotifyingBehavior notices that a page instance has been opened in a second browser window or tab. It asks the browser for the value of window.name, which reaches the server as the request parameter windowName, and remembers what the browser reported in a field of the behaviour. That field is part of the page's serialized state, so the remembered value stays in the page store for as long as the page instance does. On every later render of that page instance the behaviour builds the precondition of its Ajax call by substituting the remembered value into a single-quoted JavaScript string literal, and Wicket writes that precondition into the page as raw JavaScript, because the precondition of an Ajax call listener is script supplied by the caller and is emitted without quoting or escaping. Nothing on that path escapes the value. The window name is client-supplied and Wicket applies no validation to it, so a remembered name containing a single quote ends the literal and the rest of it runs as script in the application's origin, every time that page instance is rendered. An application is affected only where it has explicitly added AjaxNewWindowNotifyingBehavior to a component. No part of the framework installs the behaviour, so an application that does not use it is not affected. The name the behaviour generates for itself, when the browser reports no name at all, is a random UUID and is not client-supplied. This issue affects Apache Wicket: from 8.0.0 through 8.19.0, from 9.0.0 through 9.24.0, from 10.0.0 through 10.11.0. Users are recommended to upgrade to version 8.20.0, 9.25.0 or 10.12.0, which fix the issue.
Title Apache Wicket: XSS in AjaxNewWindowNotifyingBehavior via the client-supplied window name
Weaknesses CWE-79
References
Metrics cvssV4_0

{'score': 7.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-79

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 6, 2026, 2:53 PM
Reserved
Aug 31, 2026, 12:41 PM
Status
Deferred
Published
Nov 1, 2026, 11:17 PM
Modified
Nov 6, 2026, 3:17 PM