WicketApplication · Apache
CVE-2026-42509
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Apache Wicket. This issue affects Apache Wicket: from 8.0.0 through 8.17.0, 9.0.0, from 10.0.0 through 10.8.0. Users are recommended to upgrade to version 10.9.0, which fixes the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a Cross-site Scripting (XSS) vulnerability in Apache Wicket's web page generation. The framework fails to properly neutralize user-supplied input before including it in web pages, allowing attackers to inject malicious scripts that execute in the context of other users' browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
WicketApplication
>= 8.0.0, <= 8.17.0>= 9.0.0, <= 9.22.0>= 10.0.0, < 10.9.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Wicket versionExamine your project's dependency management file (pom.xml for Maven, build.gradle for Gradle) for the wicket-core dependency and its version, or list the installed Wicket JAR files.Affected if The version falls within 8.0.0 to 8.17.0, 9.0.0 to 9.22.0, or 10.0.0 to below 10.9.0
-
Locate Wicket core dependencySearch your dependency configuration for 'org.apache.wicket:wicket-core' or locate wicket-core-X.X.X.jar in your application's classpath or lib directory.Affected if Wicket core is present and matches the affected version ranges
-
Check for user input in web pagesReview your Wicket HTML templates (typically .html files in the same package as their Java counterparts) for places where user-supplied data is rendered, such as inside Label, Model, or property expressions that display request parameters, form inputs, or database content.Affected if User-controlled data is rendered without explicit output encoding using Wicket's escapeModelStrings or similar mechanisms
-
Verify output encoding configurationInspect your WebApplication class for any overrides of getMarkupSettings().setStripWicketTags() or getMarkupSettings().setComponentResolver() that may disable default escaping, and check if components use setEscapeModelStrings(false).Affected if Default output encoding is disabled or components explicitly set escapeModelStrings to false when rendering user input
-
Test for XSS injectionSubmit payloads like <script>alert(1)</script> or <img src=x onerror=alert(1)> as input to forms or URL parameters that are displayed in Wicket-generated pages and observe if the script executes in the browser.Affected if The injected script tags render as-is without HTML encoding in the response
You are affected if your application runs a Wicket version within the affected ranges AND displays user-supplied input in web pages without additional encoding safeguards.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.9.0
Upgrade Apache Wicket to version 10.9.0 or later. For organizations unable to upgrade immediately, audit all user input handling in the application and implement output encoding at the presentation layer.
10.9.0
- 1. Identify your current Apache Wicket version by checking your project's pom.xml or dependency management files
- 2. For Wicket 8.x versions (8.0.0 to 8.17.0): upgrade to the latest 8.x release or consider migrating to 10.9.0
- 3. For Wicket 9.x versions (9.0.0 to 9.22.0): upgrade to the latest 9.x release or consider migrating to 10.9.0
- 4. For Wicket 10.x versions (10.0.0 to 10.8.0): upgrade to version 10.9.0
- 5. Update the dependency version in your pom.xml (e.g., change org.apache.wicket:wicket-core from 10.8.0 to 10.9.0)
- 6. Rebuild and test your application to ensure compatibility with the new version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wicket
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42509 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42509 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data