Medium [CVE-2026-75802] Apache Wicket: AjaxEditableChoiceLabel in wicket-extensions, when constructed with a non-null IChoiceRenderer, writes the display value obtained from that renderer into the label's markup without applying the HTML escaping Wicket performs by default for component model values
This medium-severity Apache Software Foundation advisory covers CVE-2026-75802 affecting Apache Wicket.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Get an email when Apache Software Foundation publishes the next one.
VulniPulse checks Apache Software Foundation's security advisories around the clock and emails you new ones with the severity, the fixed version and the vendor's link. First month free, then US$15/month; we email you before the first charge.
Summary
AjaxEditableChoiceLabel in wicket-extensions, when constructed with a non-null IChoiceRenderer, writes the display value obtained from that renderer into the label's markup without applying the HTML escaping Wicket performs by default for component model values.
An attacker who can influence the choice or model data rendered by such a label can inject HTML or script that executes in the browser of any user who views the page. The same value is correctly escaped when the component's dropdown editor renders it as an option, so only the label rendering is affected.
AjaxEditableLabel, AjaxEditableChoiceLabel and AjaxEditableMultiLineLabel write the value returned by the protected defaultNullLabel() method into the label's markup the same way when the component's model is empty, while the model value they show otherwise is escaped.
The default implementation returns a constant, so an application is affected where it overrides that method and returns a value an attacker can influence.
Neither value could be escaped by configuration, because escapeModelStrings had no effect on any of the three components: it is read by the label they render with rather than by the component itself, and nothing carried the setting across.
This issue affects Apache Wicket: from 8.0.0 through 8.18.0, from 9.0.0 through 9.23.0, from 10.0.0 through 10.10.0.
- 8.0.0 through 8.18.0
- 9.0.0 through 9.23.0
- 10.0.0 through 10.10.0.
- through 10.10.0
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
- 8.19.0
- 9.24.0
- 10.11.0
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
Mitigation checklist
- Users are recommended to upgrade to version 8.19.0, 9.24.0 or 10.11.0, which fix the issue.
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
More Apache Software Foundation advisories
- CVE-2026-76986Aug 31, 2026Apache Wicket cross-site scripting (XSS)
- CVE-2026-76985Aug 31, 2026Apache Wicket cross-site scripting (XSS)
- CVE-2026-76983Aug 31, 2026Apache Wicket cross-site scripting (XSS)
- CVE-2026-76984Aug 31, 2026Apache Wicket cross-site scripting (XSS)
- CVE-2026-76982Aug 31, 2026Apache Wicket cross-site scripting (XSS)
- CVE-2026-71378Aug 31, 2026Apache Wicket: ResourceIsolationRequestCycleListener protects a Wicket application against
Android app · Google Play
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.