# CVE-2024-36522: Apache Wicket: Remote code execution via XSLT injection

> Attackers can execute arbitrary code via XSLT injection in Apache Wicket when processing untrusted input without validation.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jul 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-hhwc-gh8h-9rrp

## What is CVE-2024-36522?

CVE-2024-36522 is a critical code injection vulnerability in Apache Wicket, published on 12 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The default configuration of XSLTResourceStream.java is vulnerable to remote code execution via XSLT injection when processing input from an untrusted source without validation.
Users are recommended to upgrade to versions 10.1.0, 9.18.0 or 8.16.0, which fix this issue.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2024-36522?

6 open source packages ship an affected version, including org.apache.wicket:wicket-util. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.wicket:wicket-util` | Maven | From 10.0.0-M1 | 10.1.0 |
| `org.apache.wicket:wicket-util` | Maven | From 10.0.0-M1 | 10.1.0 |
| `org.apache.wicket:wicket-util` | Maven | From 8.0.0 | 8.16.0 |
| `org.apache.wicket:wicket-util` | Maven | From 8.0.0 | 8.16.0 |
| `org.apache.wicket:wicket-util` | Maven | From 9.0.0 | 9.18.0 |
| `org.apache.wicket:wicket-util` | Maven | From 9.0.0 | 9.18.0 |

Products: Apache Wicket.

## How do I fix CVE-2024-36522?

Upgrade org.apache.wicket:wicket-util to a fixed version for your release line: 10.1.0, 8.16.0 or 9.18.0.

## Is CVE-2024-36522 being exploited?

There is no known exploitation of CVE-2024-36522 in the wild and no public exploit code.

## Other vulnerabilities in Apache Wicket

- [CVE-2026-40010](https://insights.sbomify.com/CVE-2026-40010/): Apache Wicket: possible session fixation using AuthenticatedWebSession (critical 9.1)
- [CVE-2016-6793](https://insights.sbomify.com/CVE-2016-6793/): Deserialization in n/a (critical 9.1)
- [CVE-2016-6806](https://insights.sbomify.com/CVE-2016-6806/): Apache Wicket vulnerable to CSRF attacks (high 8.8)
- [CVE-2026-71257](https://insights.sbomify.com/CVE-2026-71257/): Apache Wicket: Configured file upload limits are not enforced when the multipart request has already been parsed (high 7.5)
- [CVE-2026-43646](https://insights.sbomify.com/CVE-2026-43646/): Apache Wicket: crafted URLs can bypass PackageResourceGuard (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36522 and fix it if it is affected.

What it is: CVE-2024-36522 is a critical code injection vulnerability in Apache Wicket, published on 12 Jul 2024. 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-2024-36522 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.wicket:wicket-util (Maven): affected from 10.0.0-M1; fixed in 10.1.0
- org.apache.wicket:wicket-util (Maven): affected from 10.0.0-M1; fixed in 10.1.0
- org.apache.wicket:wicket-util (Maven): affected from 8.0.0; fixed in 8.16.0
- org.apache.wicket:wicket-util (Maven): affected from 8.0.0; fixed in 8.16.0
- org.apache.wicket:wicket-util (Maven): affected from 9.0.0; fixed in 9.18.0
- org.apache.wicket:wicket-util (Maven): affected from 9.0.0; fixed in 9.18.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-2024-36522/ (Markdown: https://insights.sbomify.com/CVE-2024-36522/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-36522
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-36522
- OSV: https://osv.dev/vulnerability/CVE-2024-36522

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-36522/
Summaries are generated and may contain mistakes; the official description above is the record.