dbcve.org
WicketApplication · Apache

CVE-2024-36522

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-12
Fix available
A fix is available. Upgrade to 8.16.0 / 9.18.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

XSLTResourceStream.java has a default configuration vulnerable to remote code execution through XSLT injection. The vulnerability occurs when processing input from untrusted sources without proper validation, allowing attackers to inject malicious XSLT code that can lead to RCE.

MitigationUpgrade to versions 10.1.0, 9.18.0, or 8.16.0 which contain the fix for this vulnerability. Additionally, implement input validation for any XSLT processing from untrusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WicketApplication
Affected:>= 8.0.0, < 8.16.0>= 9.0.0, < 9.18.0= 10.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Wicket version
    Locate the wicket-core.jar file or check your project's dependency management (Maven pom.xml, Gradle build.gradle) for the org.apache.wicket:wicket-core version
    Affected if The installed version is 8.0.0 through 8.15.x, 9.0.0 through 9.17.x, or exactly 10.0.0
  2. Check for XSLTResourceStream usage
    Search your codebase for imports or references to org.apache.wicket.resource.XSLTResourceStream or XSLTResourceStream
    Affected if Your application code imports or uses XSLTResourceStream to process XML transformations
  3. Determine if untrusted XSLT input is processed
    Review code that uses XSLTResourceStream or similar XSLT processors - trace the source of XML/XSLT input (request parameters, uploaded files, external URLs)
    Affected if The application accepts XML or XSLT content from untrusted sources (user HTTP requests, uploaded files, external endpoints) and passes it to XSLT processing without validation
  4. Inspect resource loading configuration
    Examine how resource loaders are configured in your Wicket application - check WEB-INF/web.xml, application initialization code, or any ResourceStreamUrlData implementations
    Affected if The application configures custom resource streams that load XSLT content from user-controllable locations

You are affected if your Apache Wicket version falls within the vulnerable ranges AND your application uses XSLTResourceStream or similar XSLT processing with input from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.16.0 / 9.18.0 or later
Fixed in 8.16.09.18.0
Interim mitigation

Upgrade to versions 10.1.0, 9.18.0, or 8.16.0 which contain the fix for this vulnerability. Additionally, implement input validation for any XSLT processing from untrusted sources.

Recommended fix High confidence

8.16.0 (if on 8.x), 9.18.0 (if on 9.x), or 10.1.0 (if on 10.x)

  1. Identify the current Apache Wicket version in use by checking the project's dependency files (e.g., pom.xml, build.gradle, or equivalent)
  2. Determine which major version line is in use (8.x, 9.x, or 10.x)
  3. For projects using Wicket 8.x: upgrade to version 8.16.0 or later
  4. For projects using Wicket 9.x: upgrade to version 9.18.0 or later
  5. For projects using Wicket 10.x: upgrade to version 10.1.0 or later
  6. Update the version in the dependency management file and rebuild the project
  7. Verify the upgrade by running existing tests to ensure compatibility
Caveat Review release notes for any breaking changes between the current version and the target upgrade version; minor version jumps within the same major version typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wicket Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36522 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36522 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data