What is CVE-2024-36522?

CVE-2024-36522 is a high-severity security vulnerability in org.apache.wicket:wicket-util (maven), affecting versions >= 10.0.0-M1, < 10.1.0. It is fixed in 10.1.0, 9.18.0, 8.16.0.

Which versions of org.apache.wicket:wicket-util are affected by CVE-2024-36522?

org.apache.wicket:wicket-util (maven) versions >= 10.0.0-M1, < 10.1.0 is affected.

Is there a fix for CVE-2024-36522?

Yes. CVE-2024-36522 is fixed in 10.1.0, 9.18.0, 8.16.0. Upgrade to this version or later.

Is CVE-2024-36522 exploitable, and should I be worried?

Whether CVE-2024-36522 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-36522 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2024-36522 in org.apache.wicket:wicket-util

Q: Which versions of org.apache.wicket:wicket-util are affected by CVE-2024-36522?

org.apache.wicket:wicket-util (maven) versions >= 10.0.0-M1, < 10.1.0 is affected.

Q: Is there a fix for CVE-2024-36522?

Yes. CVE-2024-36522 is fixed in 10.1.0, 9.18.0, 8.16.0. Upgrade to this version or later.

Q: Is CVE-2024-36522 exploitable, and should I be worried?

Whether CVE-2024-36522 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-36522 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-36522?

Upgrade: org.apache.wicket:wicket-util to 10.1.0 or later, org.apache.wicket:wicket-util to 9.18.0 or later, org.apache.wicket:wicket-util to 8.16.0 or later.

Summary

Apache Wicket: Remote code execution via XSLT injection

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.

Impact

Affected versions

org.apache.wicket:wicket-util (>= 10.0.0-M1, < 10.1.0) org.apache.wicket:wicket-util (>= 9.0.0, < 9.18.0) org.apache.wicket:wicket-util (>= 8.0.0, < 8.16.0)

Security releases

org.apache.wicket:wicket-util → 10.1.0 (maven) org.apache.wicket:wicket-util → 9.18.0 (maven) org.apache.wicket:wicket-util → 8.16.0 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.wicket:wicket-util to 10.1.0 or later; org.apache.wicket:wicket-util to 9.18.0 or later; org.apache.wicket:wicket-util to 8.16.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-36522? CVE-2024-36522 is a high-severity security vulnerability in org.apache.wicket:wicket-util (maven), affecting versions >= 10.0.0-M1, < 10.1.0. It is fixed in 10.1.0, 9.18.0, 8.16.0.
Which versions of org.apache.wicket:wicket-util are affected by CVE-2024-36522? org.apache.wicket:wicket-util (maven) versions >= 10.0.0-M1, < 10.1.0 is affected.
Is there a fix for CVE-2024-36522? Yes. CVE-2024-36522 is fixed in 10.1.0, 9.18.0, 8.16.0. Upgrade to this version or later.
Is CVE-2024-36522 exploitable, and should I be worried? Whether CVE-2024-36522 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-36522 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-36522?
- Upgrade org.apache.wicket:wicket-util to 10.1.0 or later
- Upgrade org.apache.wicket:wicket-util to 9.18.0 or later
- Upgrade org.apache.wicket:wicket-util to 8.16.0 or later