Technical impact
The vulnerability allows a client to send WebSocket messages that are processed by any WebSocketBehavior attached to a component, even if that component is hidden, disabled, or its rendering or enabling has been rejected by the IAuthorizationStrategy. Because Wicket does not gate the onMessage calls, an attacker can trigger server‑side logic that should be restricted, potentially exposing or altering data within the component's context. No escalation to remote code execution is reported, but unauthorized invocation of business logic remains possible.
Affected Systems
All supported Apache Wicket releases from 8.0.0 through 8.19.0, 9.0.0 through 9.24.0, and 10.0.0 through 10.11.0, as well as older unsupported releases from 6.0.0 onward. The issue is fixed in version 8.20.0, 9.25.0, and 10.12.0.
Risk and Exploitability
The CVSS base score of 2.3 indicates low severity, and the EPSS score is not available. The vulnerability is not listed in CISA’s KEV catalog. The attack requires a valid user session and a page containing a component with a WebSocketBehavior; the attacker cannot affect other users, as messages are only delivered within the caller’s own session. Because the impact is limited to unauthorized method invocation on components that would otherwise be hidden, the overall risk remains low.