cve.bz

CVE-2016-6806 apache wicket: Cross Site Reference Forgery

8.8 highEPSS 0.8%Fix available

High (8.8) in apache wicket. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.wicket:wicket-core 6.25.0, 7.5.0, 8.0.0-M2.

On this page
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.

Severity

CVSS 3.0

8.8 high
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 58th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • org.apache.wicket:wicket-core (Maven): fixed in 6.25.0, 7.5.0, 8.0.0-M2

Ask an AI about this CVE

Show the promptExplain CVE-2016-6806 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2016-6806?via=ask-ai-copy and https://cve.bz/cve/CVE-2016-6806?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2016-6806 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
apache:wicket6.20.0
apache:wicket6.21.0
apache:wicket6.22.0
apache:wicket6.23.0
apache:wicket6.24.0
apache:wicket7.0.0
apache:wicket7.1.0
apache:wicket7.2.0
apache:wicket7.3.0
apache:wicket7.4.0
apache:wicket8.0.0:m1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xc66-mg8r-q6r5Mavenorg.apache.wicket:wicket-core>=6.20.0 <6.25.06.25.0
GHSA-xc66-mg8r-q6r5Mavenorg.apache.wicket:wicket-core>=7.0.0 <7.5.07.5.0
GHSA-xc66-mg8r-q6r5Mavenorg.apache.wicket:wicket-core>=8.0.0-M1 <8.0.0-M28.0.0-M2

Attack patterns (CAPEC)

  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-467 Cross Site Identification Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON