How severe is CVE-2016-6806?

CVE-2016-6806 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2016-6806 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (53rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2016-6806?

CVE-2016-6806 primarily affects Apache Wicket. In total, 11 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2016-6806?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2016-6806 published?

CVE-2016-6806 was published on 2017-10-03 and last updated on 2026-06-17.

CVE-2016-6806

CVE-2016-6806 is a high-severity vulnerability in Apache Wicket with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 6.8
EPSS exploit prediction: 1% (53rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-352
Affected product: Apache Wicket
Published: 2017-10-03
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2016-6806?: 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.
How severe is CVE-2016-6806?: CVE-2016-6806 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2016-6806 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (53rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-6806?: CVE-2016-6806 primarily affects Apache Wicket. In total, 11 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2016-6806?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2016-6806 published?: CVE-2016-6806 was published on 2017-10-03 and last updated on 2026-06-17.

References

https://lists.apache.org/thread.html/074b72585f4b7c6adda1af52aecbfe1be23c6d6f5bb9382270f059cd%40%3Cannounce.apache.org%3E

Affected products (11)

cpe:2.3:a:apache:wicket:6.20.0:*:*:*:*:*:*:*
cpe:2.3:a:apache:wicket:6.21.0:*:*:*:*:*:*:*
cpe:2.3:a:apache:wicket:6.22.0:*:*:*:*:*:*:*
cpe:2.3:a:apache:wicket:6.23.0:*:*:*:*:*:*:*
cpe:2.3:a:apache:wicket:6.24.0:*:*:*:*:*:*:*
cpe:2.3:a:apache:wicket:7.0.0:*:*:*:*:*:*:*
cpe:2.3:a:apache:wicket:7.1.0:*:*:*:*:*:*:*
cpe:2.3:a:apache:wicket:7.2.0:*:*:*:*:*:*:*
cpe:2.3:a:apache:wicket:7.3.0:*:*:*:*:*:*:*
cpe:2.3:a:apache:wicket:7.4.0:*:*:*:*:*:*:*
cpe:2.3:a:apache:wicket:8.0.0:m1:*:*:*:*:*:*

More vulnerabilities in Apache Wicket

CVE-2024-36522 — Critical (CVSS 9.8): The default configuration of XSLTResourceStream.java is vulnerable to remote code execution via XSLT injection when…
CVE-2026-40010 — Critical (CVSS 9.1): Missing invocation of Servlet http web request method changeSessionId after session binding can be exploited for…
CVE-2016-6793 — Critical (CVSS 9.1): The DiskFileItem class in Apache Wicket 6.x before 6.25.0 and 1.5.x before 1.5.17 allows remote attackers to cause a…
CVE-2026-43646 — High (CVSS 7.5): Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Wicket. This issue affects Apache…
CVE-2021-23937 — High (CVSS 7.5): A DNS proxy and possible amplification attack vulnerability in WebClientInfo of Apache Wicket allows an attacker to…
CVE-2020-11976 — High (CVSS 7.5): By crafting a special URL it is possible to make Wicket deliver unprocessed HTML templates. This would allow an…

All CVEs affecting Apache Wicket →

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

CVE-2025-32642 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in appsbd Vite Coupon vite-coupon allows Remote Code Inclusion.This…
CVE-2025-23922 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in Harsh iSpring Embedder embed-ispring allows Upload a Web Shell to a…
CVE-2017-5145 — Critical (CVSS 10.0): An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to firmware…
CVE-2019-25729 — Critical (CVSS 9.8): PDF Signer 3.0 contains a server-side template injection vulnerability that allows unauthenticated attackers to execute…
CVE-2025-48340 — Critical (CVSS 9.8): Cross-Site Request Forgery (CSRF) vulnerability in Danny Vink User Profile Meta Manager user-profile-meta allows…
CVE-2025-2907 — Critical (CVSS 9.8): The Order Delivery Date WordPress plugin before 12.3.1 does not have authorization and CSRF checks when importing…

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →