Technical impact
Apache Wicket does not enforce authorization checks before invoking component listeners when a listener URL lacks a page identifier. Because the visibility flag for the component is set only during rendering, a newly constructed page bypasses that check and the component is considered visible by default. As a result, an attacker can trigger a listener method on a component that the application intended to hide or disable. This bypass can be used to run arbitrary server‑side code, expose sensitive data, or otherwise violate application security policies.
Affected Systems
Versions of Apache Wicket from 8.0.0 through 8.19.0, from 9.0.0 through 9.24.0, and from 10.0.0 through 10.11.0 are affected. The issue is fixed in 8.20.0, 9.25.0, and 10.12.0 respectively. Applications built with any of these older releases should review their component visibility logic and update to a patched release.
Risk and Exploitability
With a CVSS score of 6.9 the vulnerability is considered moderate. The EPSS score is not provided, and the vulnerability is not listed in CISA's KEV catalog, suggesting exploitation may not be widespread yet. Because the flaw can be triggered by crafting a special listener URL—without requiring authentication or special privileges—the threat is significant for publicly exposed sites. The most likely attack vector is an unauthenticated HTTP request to the application that supplies a listener path lacking a page identifier.