CVE-2026-111089
Received Received - Intake

Cross-Site Scripting in Apache Wicket

Vulnerability report for CVE-2026-111089, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-01

Last updated on: 2026-11-01

Assigner: Apache Software Foundation

Description

Apache Wicket reads texts from the application's resource bundles β€” a localized label, a css class name β€” and writes some of them into the JavaScript and the markup it generates for a component. Those texts are placed inside single-quoted JavaScript string literals and inside quoted attribute values without being escaped for that context, so a text containing a quote ends the literal or the attribute, and what follows is parsed as script or as markup in the application's origin when the page loads. A resource bundle entry is authored for the application and does not say where the framework will write it. The same key is read by the framework into element text, where Wicket escapes it, and into the contexts below, where it did not. A text containing an apostrophe, which is ordinary in several languages, is enough to break the page; a text under the influence of another party is enough to run script. In org.apache.wicket:wicket-core, org.apache.wicket.markup.html.form.upload.MultiFileUploadField writes the org.apache.wicket.mfu.delete message into a JavaScript string literal, and org.apache.wicket.markup.html.form.Form writes the hidden-fields css class into the class attribute of the container it renders for its hidden fields; on 8.0.0 through 8.19.0 and 9.0.0 through 9.24.0 Form#appendDefaultButtonField writes the same css class into a second container. In org.apache.wicket:wicket-extensions, UploadProgressBar writes its UploadProgressBar.starting text into a JavaScript string literal, FilterForm writes the hidden-fields css class into the class attribute of its hidden input markup, and on 9.0.0 through 9.24.0 and 10.0.0 through 10.11.0 TrapFocusBehavior writes its current css class into a JavaScript string literal. The Content-Security-Policy that Apache Wicket 9.x and 10.x send by default does not prevent the JavaScript cases: the generated script is written into a script element carrying the per-response nonce, so the injected code is part of a script the policy admits. It does prevent an inline event handler injected through the attribute cases. 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 of Apache Wicket 7.x or older, which are no longer supported, should upgrade to a supported version. Users are recommended to upgrade to version 8.20.0, 9.25.0 or 10.12.0, which fix the issue.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-01
Last Modified
2026-11-01
Generated
2026-11-02
AI Q&A
2026-11-02
EPSS Evaluated
N/A
NVD

Affected Vendors & Products

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Apache Wicket improperly escapes user-controlled text when embedding it in JavaScript strings and HTML attributes. This allows attackers to inject malicious scripts or markup by including quotes in resource bundle entries, breaking out of intended contexts. The issue affects multiple components in versions 8.x, 9.x, and 10.x.

Detection Guidance

This vulnerability involves improper escaping of resource bundle texts in Apache Wicket, leading to potential XSS attacks. Detection requires checking Apache Wicket versions in use and examining JavaScript/markup generation for unescaped resource bundle entries. No specific commands are provided in the context.

Impact Analysis

An attacker could execute arbitrary JavaScript in the context of your application, steal sensitive data, or perform actions on behalf of users. Even non-malicious text like apostrophes in translations can break page functionality.

Compliance Impact

This vulnerability could lead to cross-site scripting (XSS) attacks, which may result in unauthorized data access or manipulation. For GDPR, this could violate principles of data integrity and confidentiality. For HIPAA, it might expose protected health information (PHI) to unauthorized parties.

Mitigation Strategies

Upgrade Apache Wicket to a fixed version: 8.20.0, 9.25.0, or 10.12.0. If using unsupported versions (7.x or older), upgrade to a supported release. Ensure Content-Security-Policy is properly configured to mitigate JavaScript injection risks.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-111089. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...