Technical impact
Apache Wicket may write component and markup identifiers directly into single‑quoted JavaScript literals and HTML attribute values without escaping them. If an identifier contains a single quote, backslash, double quote, or other special character, the literal can be closed, allowing arbitrary JavaScript to be executed when the page loads. This flaw is a classic unescaped XSS vulnerability (CWE‑79) that can compromise the integrity of the application and the confidentiality of users, potentially enabling data theft or session hijacking. The flaw is present only when the application supplies an identifier that includes disallowed characters; Wicket itself never introduces these characters.
Affected Systems
Apache Wicket applications from versions 8.0.0 through 8.19.0, 9.0.0 through 9.24.0, and 10.0.0 through 10.11.0 are affected. Wicket 7.x and earlier are unsupported but not vulnerable. The vulnerability triggers when a component or markup ID carries a disallowed character such as a quote, backslash, double quote, colon, tilde, parentheses, brackets, or control character. The impacted objects include form components, Ajax behaviors, and various UI widgets that embed IDs into JavaScript or markup.
Risk and Exploitability
The CVSS score of 7.6 categorizes this as a high‑severity flaw. EPSS data is not available, so the likelihood of exploitation is uncertain, but the vulnerability is active and not listed in the CISA KEV catalog. Attackers do not need special permissions; by controlling the component IDs in the application code or submitted data, they can inject payloads that execute in the browser under the same origin. Because the generated script is run with a per‑response nonce, standard Content‑Security‑Policy settings do not block the injection. The flaw can be exploited during normal page rendering, making it a broad exposure for any affected web application.