How severe is CVE-2020-11976?

CVE-2020-11976 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-11976?

CVE-2020-11976 affects the following packages: org.apache.wicket:wicket-core (Maven), org.apache.wicket:wicket-core (Maven), org.apache.wicket:wicket-core (Maven), org.apache.wicket:wicket-core (Maven), org.apache.wicket:wicket-core (Maven), org.apache.wicket:wicket-core (Maven), org.apache.wicket:wicket-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-11976?

Update org.apache.wicket:wicket-core to 7.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-11976 is resolved across your whole dependency graph.

How do I detect CVE-2020-11976 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.wicket:wicket-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2020-11976 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2020-11976 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-11976 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2020-11976?

CVE-2020-11976 has an EPSS (Exploit Prediction Scoring System) score of 3.8%, placing it in the 90th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2020-11976?

CVE-2020-11976 is classified as CWE-552 (CWE-552). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-11976 published, and has it been updated?

CVE-2020-11976 was published on August 11, 2020 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2020-11976 — wicket-core

HIGH

CVE-2020-11976 is a high-severity (CVSS 7.5) CWE-552 vulnerability in org.apache.wicket:wicket-core. A fix is available for org.apache.wicket:wicket-core — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in Apache Wicket

Also known asGHSA-64gv-3pqv-299h

Published

Aug 11, 2020

Updated

Oct 24, 2026

Affected

7 pkgs

Patched

7 / 7

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

7 pkgs affected

☕org.apache.wicket:wicket-core☕org.apache.wicket:wicket-core☕org.apache.wicket:wicket-core☕org.apache.wicket:wicket-core☕org.apache.wicket:wicket-core☕org.apache.wicket:wicket-core☕org.apache.wicket:wicket-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

By crafting a special URL it is possible to make Wicket deliver unprocessed HTML templates. This would allow an attacker to see possibly sensitive information inside a HTML template that is usually removed during rendering. Affected are Apache Wicket versions 7.16.0, 8.8.0 and 9.0.0-M5

Affected Packages

7 total 7 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.wicket:wicket-core`	all versions	7.17.0`org.apache.wicket:wicket-core:7.17.0`
☕Maven	`org.apache.wicket:wicket-core`	≥ 8.0.0&&< 8.9.0	8.9.0`org.apache.wicket:wicket-core:8.9.0`
☕Maven	`org.apache.wicket:wicket-core`	≥ 9.0.0-M1&&< 9.0.0	9.0.0`org.apache.wicket:wicket-core:9.0.0`
☕Maven	`org.apache.wicket:wicket-core`	≥ 9.0.0-M2&&< 9.0.0	9.0.0`org.apache.wicket:wicket-core:9.0.0`
☕Maven	`org.apache.wicket:wicket-core`	≥ 9.0.0-M3&&< 9.0.0	9.0.0`org.apache.wicket:wicket-core:9.0.0`
☕Maven	`org.apache.wicket:wicket-core`	≥ 9.0.0-M4&&< 9.0.0	9.0.0`org.apache.wicket:wicket-core:9.0.0`

Affected Products

2 products · 8 configurations

Application

fortressapache

1 version

2.0.5

Application

wicketapache

≥ 8.0.0 && < 8.9.0

1 version

9.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.wicket:wicket-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.wicket:wicket-core to 7.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-11976 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-11976 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works