dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36224

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to 6.5.21 / 2024.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Adobe Experience Manager versions 6.5.20 and earlier Answer: are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability. This vulnerability could allow an attacker to execute arbitrary JavaScript code in the context of the victim's browser session. Exploitation of this issue typically requires user interaction, such as convincing a user to click on a specially crafted link or to submit a form that causes the vulnerable script to execute.

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

A DOM-based Cross-Site Scripting vulnerability in Adobe Experience Manager versions 6.5.20 and earlier allows attackers to inject malicious JavaScript into pages viewed by victims. The vulnerability requires user interaction such as clicking a crafted link or submitting a malicious form.

MitigationUpgrade to AEM 6.5.21 or later to apply the security patch, and implement Content Security Policy (CSP) headers to provide defense-in-depth against XSS attacks.

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
Experience ManagerApplication
Affected:< 6.5.21< 2024.5

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Check AEM version in the OSGi console
    Navigate to the AEM Web Console (typically at /system/console/bundles) or access the product info page at /crx/packmgr/service.jsp?cmd=version to retrieve the installed AEM version number
    Affected if The installed version is 6.5.20 or earlier, or the version is below 2024.5 (for newer release trains)
  2. Verify the AEM release train
    Check the product version by accessing the AEM Welcome page or the About Adobe Experience Manager option in the Help menu. Identify whether it follows the 6.5.x cycle or the year-based 2024.x cycle
    Affected if The version displays as 6.5.20 or lower, or as 2024.1 through 2024.4 (if year-based)
  3. Confirm DOM-based XSS exposure
    Review the application's user-generated content handling and any custom components that process URL parameters or form inputs client-side. Look for instances where URL fragments, query parameters, or form data are directly inserted into the DOM without proper sanitization
    Affected if The AEM instance hosts custom components or forms that accept user input and render it directly into HTML without encoding, enabling the DOM XSS attack vector
  4. Assess user interaction vectors
    Examine whether the AEM instance exposes publish-facing forms, comment systems, or pages that could accept malicious links. Check if external URL parameters are used in client-side JavaScript
    Affected if The environment allows unauthenticated or low-privileged users to submit content, or exposes pages that accept URL parameters processed by client-side scripts

You are affected if your installed AEM version is 6.5.20 or earlier, or falls between 2024.1 and 2024.4, and your instance processes user input or URL parameters client-side without sanitization.

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 6.5.21 / 2024.5 or later
Fixed in 6.5.212024.5
Interim mitigation

Upgrade to AEM 6.5.21 or later to apply the security patch, and implement Content Security Policy (CSP) headers to provide defense-in-depth against XSS attacks.

Recommended fix High confidence

AEM 6.5.21 or AEM 2024.5 (depending on your release track)

  1. Upgrade Adobe Experience Manager to version 6.5.21 or later if running 6.5.x release track
  2. If running the newer release cadence, upgrade to version 2024.5 or later
  3. After upgrading, verify the installation was successful by checking the AEM version in the About Adobe Experience Manager page
  4. Review the release notes for the new version to ensure no regressions in your specific configuration
  5. Test to confirm the DOM-based XSS vulnerability is no longer present
Caveat Review release notes for potential compatibility changes, though patch releases typically have minimal breaking changes

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36224 — 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-36224 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