dbcve.org
WicketApplication · Apache

CVE-2016-6806

HIGH · 8.8 CVSS v3.0 Published 2017-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Apache Wicket 6.x before 6.25.0, 7.x before 7.5.0, and 8.0.0-M1 provide a CSRF prevention measure that fails to discover some cross origin requests. The mitigation is to not only check the Origin HTTP header, but also take the Referer HTTP header into account when no Origin was provided. Furthermore, not all Wicket server side targets were subjected to the CSRF check. This was also fixed.

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 confidence

Apache Wicket's CSRF prevention mechanism failed to properly validate cross-origin requests by only checking the Origin HTTP header without falling back to the Referer header when Origin was absent. Additionally, not all Wicket server-side targets were subject to CSRF validation, allowing some endpoints to bypass the protection entirely.

MitigationUpgrade to Apache Wicket 6.25.0, 7.5.0, 8.0.0 or later, which includes proper Referer header checking when Origin is missing and applies CSRF validation to all server-side targets.

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
Affected:= 6.20.0= 6.21.0= 6.22.0= 6.23.0= 6.24.0= 7.0.0= 7.1.0= 7.2.0= 7.3.0= 7.4.0= 8.0.0

CVSS 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Apache Wicket is in use
    Search for Wicket libraries in your application deployment (e.g., look for wicket-*.jar files in WEB-INF/lib or check Maven/Gradle dependencies for org.apache.wicket artifacts)
    Affected if Apache Wicket libraries are present in the application
  2. Determine installed Wicket version
    Check the exact version of the Wicket JAR files (e.g., wicket-core-x.x.x.jar) or examine the Maven/Gradle dependency tree for org.apache.wicket:wicket-core
    Affected if The version is 6.20.0, 6.21.0, 6.22.0, 6.23.0, 6.24.0, 7.0.0, 7.1.0, 7.2.0, 7.3.0, 7.4.0, or 8.0.0
  3. Verify CSRF protection is enabled
    Check your Wicket configuration (Application class) for CSRF settings. Look for any calls to getSecuritySettings().setCsrfPreventionEnabled() or examine web.xml for Wicket filter configuration. The default setting enables CSRF protection for form submissions.
    Affected if CSRF prevention is enabled (which is the default behavior)
  4. Check for server-side targets or AJAX endpoints
    Review your Wicket pages and components for server-side targets. Inspect code for usages of ajaxPostEventHandler, ajaxPostSubmitHandler, or server-side onClick handlers that handle sensitive operations without custom CSRF tokens.
    Affected if The application uses Wicket AJAX handlers or server-side targets that rely solely on Wicket's built-in CSRF validation

You are affected if your application runs Apache Wicket versions 6.20.0 through 8.0.0 and uses Wicket's built-in CSRF protection for form submissions or AJAX endpoints without custom token validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Apache Wicket 6.25.0, 7.5.0, 8.0.0 or later, which includes proper Referer header checking when Origin is missing and applies CSRF validation to all server-side targets.

Fix this in Wicket Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-6806 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-6806 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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