Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify Wicket app wrapping handlers in nested delegates
-
DeliveryFind content-injection point on affected page
-
ExploitMissing CSP header leaves inline scripts unguarded
-
ExecutionVictim loads page and injected script executes
-
ImpactContent/session abuse in victim browser
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Protection mechanism completeness
|
| Exploitation Conditions | Exploitation requires a non-default deployment where the application wraps a page's render request handler in more than one IRequestHandlerDelegate (a delegate chain deeper than one level - e.g. an application-provided delegating request mapper combined with CryptoMapper), AND CSP must be enabled in the application; under these conditions the affected page is served with no CSP header and the nonce-based inline-script/style protection is lost. The affected versions are exactly 10.10.0, 10.11.0 and 9.24.0; versions before 10.10.0 and 9.24.0 handled nested delegates correctly. Limiting factors: stock Wicket applications that do not wrap request handlers themselves are not affected; the flaw only removes a protective control, so actual content injection also requires a separate injection vector on the page plus a victim rendering it (passive user interaction). |
| Impact | All signals point to a genuinely low priority. The input CVSS 4.0 score is 2.3 (Low) with VC:N/VI:N/VA:N - there is no direct impact on the vulnerable system; only subsequent-system confidentiality and integrity are rated Low (SC:L/SI:L), reflecting that this is a protection-mechanism failure (CWE-693) rather than a directly exploitable flaw. The vuln.today decision label is 'monitor', the lowest urgency tier, and the vulnerability is not in CISA KEV, has no public exploit identified at time of analysis, and no EPSS score was provided. Crucially, the flaw only manifests when the application itself wraps request handlers in more than one IRequestHandlerDelegate - stock Wicket applications are explicitly stated to be unaffected - so the real-world exposed population is a subset of an already modest user base. The net effect is loss of a defense-in-depth control (CSP nonce protection), which has no impact unless a separate content-injection vulnerability already exists on an affected page. The AT:P (attack requirement present) and UI:P (passive user interaction) metrics are consistent with the description's requirement for a specific non-default handler-wrapping configuration and a victim rendering the affected page. This is a high-correctness, low-real-risk hardening fix, not an emergency. |
| Exploit ScenarioDerived | An application built on Apache Wicket 10.10.0/10.11.0/9.24.0 that combines a custom delegating request mapper with CryptoMapper serves certain pages with no Content-Security-Policy header, silently dropping the nonce-based inline-script/style protection. If such a page also contains a content-injection sink, an attacker can inject inline script or style that the CSP was meant to block, and it executes when a victim loads the page. No public exploit is identified at time of analysis, and the weakness is only reachable in non-default configurations where the application wraps request handlers in a nested delegate chain. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 01, 2026
Pages rendered by Apache Wicket 10.10.0, 10.11.0 and 9.24.0 can be served without any Content-Security-Policy header when the page's render request handler is wrapped in more than one IRequestHandlerDelegate, because the framework unwraps only a single delegate level when deciding whether a request renders a page; with a deeper chain - for example an application-provided delegating request mapper combined with CryptoMapper - CSP is silently skipped with no error or warning, and the nonce-based protection for inline scripts and styles plus any other configured directives are lost for those pages. Only applications that wrap request handlers themselves in a non-default deployment are exposed; stock Wicket applications are not affected, and because the defect removes a protective control rather than providing an injection primitive, actual content injection additionally requires a separate injection vector on such a page and a victim rendering it (passive user interaction). This is a low-severity, configuration-dependent regression - versions before 10.10.0 and 9.24.0 handled nested delegates correctly - and no public exploit has been identified at time of analysis, with CISA KEV status absent and the vulnerability not listed as actively exploited.
RemediationAI
Upgrade to Apache Wicket 10.12.0 (10.x line) or 9.25.0 (9.x line), the versions the vendor states fix this issue; no other patch version is identified in the available data. Because the defect only appears when a page's render handler sits behind more than one IRequestHandlerDelegate, applications that cannot upgrade immediately should verify whether they actually compose multiple delegating handlers on the same render path - the advisory's example being an application-provided delegating request mapper combined with CryptoMapper - and, where they do, collapse the chain to a single delegate level so the CSP header is emitted again, accepting the application-design constraint that this imposes. Pushing a static Content-Security-Policy header from the servlet container or reverse proxy is an alternative, but it would not carry Wicket's per-request nonce, so inline scripts and styles relying on nonce authorisation would break unless they are moved out of line or allowlisted by other means. Operators should also confirm in responses that the CSP header is actually present on affected pages, since the failure is silent and produces no error or warning. Vendor advisory: https://lists.apache.org/thread.html/fjq8v35zpkbtjwpzwkkpzocwtdgokp1m.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache Wicket is a Java component-based web framework in which request handling is layered through IRequestHandler implementations; a page's render handler can be wrapped by IRequestHandlerDelegate instances, and Wicket's CSP support decides whether to emit the Content-Security-Policy header by inspecting the handler chain to determine whether the request renders a page. The root cause is CWE-693 (Protection Mechanism Failure): in 10.10.0, 10.11.0 and 9.24.0 the unwrapping logic inspects only one delegate level, so a chain two or more levels deep - the advisory's example combines an application-supplied delegating request mapper with CryptoMapper, Wicket's URL-encryption mapper - is not recognised as a page render and the CSP header (carrying the per-request nonce used to authorise Wicket's inline scripts and styles, plus any other application-configured directives) is omitted without any error or warning. This is a regression introduced in those releases; earlier versions resolved nested delegates correctly. The impact surface is therefore not the CSP machinery itself but any application that both enables CSP and composes delegating mappers/handlers on the same page render path, where the missing header re-enables content injection that the policy was configured to block. Note that the assessed severity reflects that the flaw only strips a defensive header in a non-default deployment, not that it grants an attacker a direct code path.
Know when Apache Wicket gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/AU:N/RE:L
Requires a non-default nested-delegate handler configuration (AC:H) and a victim loading the page (UI:R); the server flaw weakens protection in the user's browser (S:C) enabling limited content injection (C:L/I:L).
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
DescriptionCVE.org
Apache Wicket 10.10.0, 10.11.0 and 9.24.0 do not set the Content-Security-Policy headers on a page whose render request handler is wrapped in more than one IRequestHandlerDelegate. The framework unwraps only a single delegate level when deciding whether a request renders a page, so with a deeper chain, for example an application-provided delegating request mapper combined with CryptoMapper, the page is served without any CSP header even though CSP is enabled, and no error or warning is raised. The nonce-based protection Wicket applies to inline scripts and styles, together with any other CSP directives configured by the application, is thereby lost for those pages, exposing them to content injection the policy was meant to prevent. Applications on stock Wicket that do not wrap request handlers themselves are not affected. Versions before 10.10.0 and 9.24.0 handled nested delegates correctly. Users are recommended to upgrade to version 10.12.0 or 9.25.0, which fix the issue.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
More in Apache Wicket
View allPath traversal vulnerability in Apache Wicket's FolderUploadsFileManager allows unauthenticated attackers to read arbitr
Apache Wicket's form-less upload endpoint (AbstractFileUploadResource, the server side of FileUploadToResourceField, or
Heap-exhaustion denial of service in Apache Wicket 9.14.0 through 9.24.0 and 10.0.0 through 10.11.0, reachable without a
Cross-site scripting in Apache Wicket 8.0.0 through 8.19.0, 9.0.0 through 9.24.0 and 10.0.0 through 10.11.0 allows text
Cross-site scripting in Apache Wicket 8.0.0 through 8.19.0, 9.0.0 through 9.24.0 and 10.0.0 through 10.11.0 lets a value
Stored cross-site scripting in Apache Wicket's AjaxNewWindowNotifyingBehavior allows a client-supplied browser window na
Cross-site scripting in Apache Wicket 8.0.0 through 8.19.0 lets remote attackers get script executed in the application'
Apache Wicket's public JavaScriptUtils.escapeQuotes() helper fails to escape backslashes before quotes, so attacker-infl
Cross-site scripting in Apache Wicket's SmartLinkLabel and SmartLinkMultiLineLabel components turns attacker-influenced
Session fixation in Apache Wicket's role-based authentication module leaves the container session id unchanged when an a
Missing authorization in Apache Wicket 8.x, 9.x and 10.x allows unauthenticated remote attackers to invoke a component's
Missing authorization in Apache Wicket 10.3.0 through 10.11.0 allows a remote unauthenticated caller to invoke the serve
EUVD-2026-114902
GHSA-58xq-c93x-4pwm
NVD
CVE.org
EPSS
Exploit-DB