CVE-2026-82956High· 7.6▾ TwilightImproper 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 …
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 41.8 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.3%
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.
org.apache.wicket:wicket-core >= 8.0.0 <= 8.19.0org.apache.wicket:wicket-core >= 9.0.0 <= 9.24.0org.apache.wicket:wicket-core >= 10.0.0 <= 10.11.0Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-111089High· 7.6Apache Wicket: XSS via a resource bundle text written unescaped into generated JavaScript and markup
CVE-2026-95863High· 7.6Apache Wicket: XSS via a component id or markup id written unescaped into generated JavaScript and markup
CVE-2026-84231High· 7.4Apache Wicket: XSS in ExternalLink via the model URL when the component is bound to a non-anchor tag
CVE-2026-84177Medium· 6.3Apache Wicket: A component's markup is served as a package resource when its class name contains an underscore
CVE-2026-87718Low· 2.3Apache Wicket: CSP headers silently omitted for pages served through nested request handler delegates
CVE-2026-83594High· 8.3Apache Wicket: FileUploadToResourceField accepts a client-asserted upload result and allocates the size it names