Technical impact
The flaw in Apache Wicket’s WebSocket message broadcast handler allows a request handler to deliver incoming frames directly to a shared WebSocketResource without consulting the framework’s IAuthorizationStrategy. As a result, an authenticated user bound to a Wicket session can provide the public resource name, establish a WebSocket connection, and invoke any of the resource’s callbacks—including onConnect and the onMessage methods—without any access control check. This can lead to execution of arbitrary application logic or data manipulation within the scope of that user’s session.
Affected Systems
Apache Software Foundation’s Apache Wicket framework is affected for all supported releases from 8.0.0 through 8.19.0, from 9.0.0 through 9.24.0, from 10.0.0 through 10.11.0, and older unsupported releases from 7.0.0 onward. The vulnerability exists when a WebSocketResource is registered as a shared resource and relies on the framework’s configured authorization strategy to restrict access.
Risk and Exploitability
With a CVSS score of 6.3 the vulnerability is considered moderately severe. The EPSS score is not available and the vulnerability is not listed in CISA KEV, indicating no known widespread exploitation. The attack requires a valid Wicket session and the public resource name, both of which are accessible to an attacker from the client side. An attacker can send arbitrary message payloads over the established WebSocket connection, potentially triggering unintended application logic, but the connection remains scoped to the attacker’s own session and does not allow cross‑user session hijacking.