# CVE-2020-11976: Exposure of Sensitive Information to an Unauthorized Actor in Apache Wicket > Attackers can view sensitive data in unprocessed HTML templates by crafting special URLs in Apache Wicket applications. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 11 Aug 2020 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-64gv-3pqv-299h ## What is CVE-2020-11976? CVE-2020-11976 is a high-severity vulnerability in Apache Wicket, published on 11 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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 Weakness: CWE-552 (Files or Directories Accessible to External Parties) ## Which versions are affected by CVE-2020-11976? 14 open source packages ship an affected version, including org.apache.wicket:wicket-core. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.wicket:wicket-core` | Maven | All versions | 7.17.0 | | `org.apache.wicket:wicket-core` | Maven | All versions | 7.17.0 | | `org.apache.wicket:wicket-core` | Maven | From 8.0.0 | 8.9.0 | | `org.apache.wicket:wicket-core` | Maven | From 8.0.0 | 8.9.0 | | `org.apache.wicket:wicket-core` | Maven | From 9.0.0-M1 | 9.0.0 | | `org.apache.wicket:wicket-core` | Maven | From 9.0.0-M1 | 9.0.0 | | `org.apache.wicket:wicket-core` | Maven | From 9.0.0-M2 | 9.0.0 | | `org.apache.wicket:wicket-core` | Maven | From 9.0.0-M2 | 9.0.0 | | `org.apache.wicket:wicket-core` | Maven | From 9.0.0-M3 | 9.0.0 | | `org.apache.wicket:wicket-core` | Maven | From 9.0.0-M3 | 9.0.0 | | `org.apache.wicket:wicket-core` | Maven | From 9.0.0-M4 | 9.0.0 | | `org.apache.wicket:wicket-core` | Maven | From 9.0.0-M4 | 9.0.0 | | `org.apache.wicket:wicket-core` | Maven | From 9.0.0-M5 | 9.0.0 | | `org.apache.wicket:wicket-core` | Maven | From 9.0.0-M5 | 9.0.0 | Products: Apache Fortress, Apache Wicket. ## How do I fix CVE-2020-11976? Upgrade org.apache.wicket:wicket-core to a fixed version for your release line: 7.17.0, 8.9.0 or 9.0.0. ## Is CVE-2020-11976 being exploited? There is no known exploitation of CVE-2020-11976 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-11976 and fix it if it is affected. What it is: CVE-2020-11976 is a high-severity vulnerability in Apache Wicket, published on 11 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-11976 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.wicket:wicket-core (Maven): affected all versions; fixed in 7.17.0 - org.apache.wicket:wicket-core (Maven): affected all versions; fixed in 7.17.0 - org.apache.wicket:wicket-core (Maven): affected from 8.0.0; fixed in 8.9.0 - org.apache.wicket:wicket-core (Maven): affected from 8.0.0; fixed in 8.9.0 - org.apache.wicket:wicket-core (Maven): affected from 9.0.0-M1; fixed in 9.0.0 - org.apache.wicket:wicket-core (Maven): affected from 9.0.0-M1; fixed in 9.0.0 - org.apache.wicket:wicket-core (Maven): affected from 9.0.0-M2; fixed in 9.0.0 - org.apache.wicket:wicket-core (Maven): affected from 9.0.0-M2; fixed in 9.0.0 - org.apache.wicket:wicket-core (Maven): affected from 9.0.0-M3; fixed in 9.0.0 - org.apache.wicket:wicket-core (Maven): affected from 9.0.0-M3; fixed in 9.0.0 - org.apache.wicket:wicket-core (Maven): affected from 9.0.0-M4; fixed in 9.0.0 - org.apache.wicket:wicket-core (Maven): affected from 9.0.0-M4; fixed in 9.0.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-11976/ (Markdown: https://insights.sbomify.com/CVE-2020-11976/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-11976 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-11976 - OSV: https://osv.dev/vulnerability/CVE-2020-11976 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-11976/ Summaries are generated and may contain mistakes; the official description above is the record.