Exposure of Sensitive Information to an Unauthorized Actor in Apache Wicket

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2020-11976: 3.76% estimated exploitation activity in the next 30 days; percentile 89.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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

Published by the source

7 May 2021, 15:54 UTC

Last modified by the source

1 Feb 2023, 05:05 UTC

Source last checked

26 Oct 2026, 16:06 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-64gv-3pqv-299h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-11976

Advisory: Exposure of Sensitive Information to an Unauthorized Actor in Apache Wicket
IDs: CVE-2020-11976, GHSA-64gv-3pqv-299h
Record: https://patchnext.com/advisories/cve-2020-11976 (revision 1, source checked 26 Oct 2026, 16:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.wicket:wicket-core 9.0.0, 8.9.0, 7.17.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.wicket:wicket-core: affected < 7.17.0; >= 8.0.0, < 8.9.0; >= 9.0.0-M1, <= 9.0.0-M1; >= 9.0.0-M2, <= 9.0.0-M2; >= 9.0.0-M3, <= 9.0.0-M3; >= 9.0.0-M4, <= 9.0.0-M4; >= 9.0.0-M5, <= 9.0.0-M5; fixed in 9.0.0, 8.9.0, 7.17.0

## Suggested inspection (read-only)
- Maven org.apache.wicket:wicket-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.wicket:wicket-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-64gv-3pqv-299h (GitHub-reviewed advisory GHSA-64gv-3pqv-299h lists affected ranges: Maven org.apache.wicket:wicket-core >=0 =8.0.0 =9.0.0-M1 =9.0.0-M2 =9.0.0-M3 =9.0.0-M4 =9.0.0-M5 <=9.0.0-M5)

Commands are suggestions: review each one before running it.