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.
CVE-2016-6806
HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 63% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EPSS
- 53.0%
- KEV
- Not listed
Published
October 3, 2017
Last Modified
May 13, 2026
Advisory Details (1)
Auto-updated May 23, 2026No patch confirmed yet.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| org.apache.wicket:wicket-core | 8.0.0-M1 | 8.0.0-M2 | — |
Frequently asked(5)
What is CVE-2016-6806?
CVE-2016-6806 is a high vulnerability published on October 3, 2017. 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.…
When was CVE-2016-6806 disclosed?
CVE-2016-6806 was first published in the National Vulnerability Database on October 3, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-6806 actively exploited?
CVE-2016-6806 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 53.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-6806?
CVE-2016-6806 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2016-6806?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-6806, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-6806
Is Your Infrastructure Affected by CVE-2016-6806?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.