Skip to content
Sign in
CVE-2026-958637.6High

Apache Wicket: XSS via a component id or markup id written unescaped into generated JavaScript and markup

Apache Software Foundation · Apache Wicket

Not in CISA KEVVendor fix available

No EPSS score yet. The score appears once FIRST publishes it.

7.6HighCVSS
LowHigh

DescriptionNVD

Improper neutralization of input during web page generation in Apache Wicket. Apache Wicket generates JavaScript that refers to the elements it renders, and writes into that JavaScript two values it derives itself: a component's markup id, and the input name of a form component, which is built from component ids. Both are placed inside single-quoted JavaScript string literals without being escaped for that context, so a value containing a single quote or a backslash ends the literal, and what follows is parsed as script and runs in the application's origin when the page loads. A markup id is the value passed to org.apache.wicket.Component#setMarkupId(String), or the id attribute written in the component's markup, or an id Wicket generates, in that order. The first two are supplied by the application in an HTML context, where both characters are legal and where Wicket escapes them correctly when it writes the same value into the id attribute of the element; a generated id cannot contain either. An input name is derived from the ids of the components between the form and the form component, and a component id was rejected only for ':' and '~'. In org.apache.wicket:wicket-core on 9

Coverage1 article · 1 outlet

First in our coverage: SecurityOnline, 2 Nov.

  1. Apache Wicket fixes 19 flaws across three supported releases
    SecurityOnline · first in our coverage · mentions it in passing

New articles also arrive in the RSS feed.

References

Updated AboutDevelopersSign in