Technical impact
Apache Wicket versions 10.10.0, 10.11.0 and 9.24.0 incorrectly omit the Content‑Security‑Policy header for pages whose render request handler is wrapped in more than one IRequestHandlerDelegate. The framework only checks a single delegate layer when determining if a request renders a page; deeper nesting causes the CSP header to be silent, even when CSP is enabled. As a result, the nonce‑based protection that Wicket applies to inline scripts and styles is lost, allowing an attacker to inject malicious content into those pages. This weakness corresponds to CWE‑693, improper enforcement of security controls, and presents a risk to confidentiality and integrity of the web application content.
Affected Systems
The affected products are Apache Wicket from the Apache Software Foundation. Vulnerable releases are 10.10.0, 10.11.0, and 9.24.0. Applications that do not wrap request handlers are not affected. The issue is fixed in Apache Wicket 10.12.0 and 9.25.0.
Risk and Exploitability
The CVSS score of 2.3 indicates low overall severity, and the EPSS score is not available. The vulnerability is not listed in CISA KEV. Exploitation is theoretically possible when an application uses nested request handler delegates—such as a custom delegating request mapper combined with CryptoMapper—because the nested structure leads to the omission of the CSP header. However, the core condition requires specific application configuration, so the likelihood of widespread exploitation is limited but should not be ignored. The attacker would still need network access to the target application to inject content, but once achieved, the page could be compromised due to the missing CSP protections.