CVE-2026-111089

Apache Wicket: XSS via a resource bundle text written unescaped into generated JavaScript and markup

Published Nov 1, 2026 CVSS 4.0 · 7.6 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Apache Wicket reads localized text from application resource bundles and writes them directly into generated JavaScript string literals and HTML attribute values without escaping for the target context. A resource bundle entry that contains an apostrophe or other quote character therefore terminates the literal or attribute and allows an attacker to inject arbitrary script or markup that the browser executes when the page loads. This flaw creates a classic cross‑site scripting (XSS) vulnerability in the rendered page.

Affected Systems

Apache Wicket 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. The issue is fixed in the supported releases 8.20.0, 9.25.0, and 10.12.0. Older 7.x or earlier releases are unsupported and should also be updated.

Risk and Exploitability

The CVSS score of 7.6 indicates a high impact severity. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is that an attacker who can alter a resource bundle entry—including placeholders used by the application—can inject malicious payloads. The client's browser then executes the injected code with the privileges of the page, enabling typical XSS abuses such as credential phishing, data theft, or session hijacking. Because the flaw is client‑side, no server‑side privileges are required, but it can impact any user who views the vulnerable page.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Wicket to a patched version (8.20.0, 9.25.0, or 10.12.0) to eliminate the unescaped-injection flaw.
  • If an upgrade is not immediately possible, remove or sanitize any resource bundle entries that may contain unescaped quote characters before they are rendered in JavaScript or attribute contexts.
  • Apply server‑side validation or context‑aware escaping to all dynamic content that is inserted into JavaScript string literals or HTML attributes, ensuring that any user‑controlled or developer‑supplied text is properly escaped.

Generated by OpenCVE AI on November 1, 2026 at 23:20 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 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.
Title Apache Wicket: XSS via a resource bundle text written unescaped into generated JavaScript and markup
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:38 PM
Reserved
Oct 15, 2026, 2:55 PM
Status
Deferred
Published
Nov 1, 2026, 11:17 PM
Modified
Nov 6, 2026, 3:17 PM