WicketApplication · Apache
CVE-2024-27439
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 · uneditedAn error in the evaluation of the fetch metadata headers could allow a bypass of the CSRF protection in Apache Wicket. This issue affects Apache Wicket: from 9.1.0 through 9.16.0, and the milestone releases for the 10.0 series. Apache Wicket 8.x does not support CSRF protection via the fetch metadata headers and as such is not affected. Users are recommended to upgrade to version 9.17.0 or 10.0.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 confidenceApache Wicket versions 9.1.0 through 9.16.0 and 10.0 milestone releases contain a flaw in how fetch metadata headers (Sec-Fetch-Site, Sec-Fetch-Mode, Sec-Fetch-User) are evaluated, allowing attackers to bypass CSRF protection mechanisms that rely on these headers.
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
>= 9.1.0, < 9.17.0= 10.0.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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 version in useLocate the wicket-core jar file or check build configuration (pom.xml, gradle dependencies) for the wicket-core dependency versionAffected if The installed version falls within 9.1.0 through 9.16.0 or equals 10.0.0
-
Determine if fetch metadata CSRF protection is enabledInspect application configuration files and code for CSRF protection settings, specifically looking for configurations that reference Sec-Fetch-Site, Sec-Fetch-Mode, or Sec-Fetch-User headersAffected if The application uses CSRF protection that validates fetch metadata headers (Sec-Fetch-*)
-
Check the WebApplication or Security settings for CSRF validator configurationSearch source code for org.apache.wicket.csrf.SecuredPageParametersFeature, CSRF settings, or custom filter configurations that validate fetch metadata headersAffected if A custom or default CSRF validator relying on fetch metadata headers is configured and active
-
Verify the HttpServletRequest processing for fetch metadata headersReview application code that inspects Sec-Fetch-Site, Sec-Fetch-Mode, or Sec-Fetch-User request headers for security decisionsAffected if The application code processes these headers for access control or CSRF validation purposes
You are affected if your Apache Wicket version is 9.1.0-9.16.0 or 10.0.0 AND your application uses CSRF protection that relies on validating Sec-Fetch-Site, Sec-Fetch-Mode, or Sec-Fetch-User headers.
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 · scoped9.17.0
Upgrade to Apache Wicket 9.17.0 or 10.0.0 which contain the corrected fetch metadata header validation logic.
9.17.0 (or latest 10.x release)
- 1. Identify your current Apache Wicket version in your project dependencies (e.g., pom.xml, build.gradle)
- 2. Update the Wicket dependency version to 9.17.0 for users on the 9.x line, or to the latest 10.x release if migrating to version 10
- 3. For Maven projects, update the version in pom.xml: change <version>9.x.x</version> to <version>9.17.0</version>
- 4. Run your project's build and test suite to verify the upgrade does not break existing functionality
- 5. Verify that the fetch metadata CSRF protection is working correctly after the upgrade
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 / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27439 — 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-2024-27439 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