dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36222

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 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 victim to click on a specially crafted link or to submit a form that triggers the vulnerability.

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

Adobe Experience Manager versions 6.5.20 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability. The vulnerability allows attackers to execute arbitrary JavaScript in the context of a victim's browser session via malicious links or crafted form submissions.

MitigationUpgrade to a patched Adobe Experience Manager version beyond 6.5.20 and implement output encoding on user-supplied data to prevent XSS execution.

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. Determine installed AEM version
    Access the AEM Web Console Status page (typically at /system/console/status) or locate the version.properties file in the crx-quickstart folder. The version is displayed as 'Adobe Experience Manager' with a version number.
    Affected if The displayed version is 6.5.20 or earlier, or falls below 2024.5 (for cloud/flexible packaging).
  2. Verify version against affected ranges
    Compare the identified version number to the affected ranges: any version < 6.5.21 or < 2024.5 is considered vulnerable.
    Affected if The installed version matches any range below the patched versions (6.5.21+ or 2024.5+).
  3. Identify custom components accepting user input
    Review any custom AEM components, forms, or TouchUI widgets that handle URL parameters, form submissions, or user-supplied content. Inspect the client-side JavaScript for direct insertion of raw input into the DOM.
    Affected if Custom components or scripts directly render URL parameters or form data into HTML without proper output encoding or sanitization.

The environment is affected if the installed Adobe Experience Manager version is 6.5.20 or earlier, or any version below 2024.5, and the system processes user-supplied data through vulnerable client-side code paths.

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 a patched Adobe Experience Manager version beyond 6.5.20 and implement output encoding on user-supplied data to prevent XSS execution.

Recommended fix Moderate confidence

Adobe Experience Manager 6.5.21 or 2024.5 (depending on your release track)

  1. 1. Backup your current Adobe Experience Manager instance and all content repositories before proceeding with the upgrade.
  2. 2. Review the Adobe Experience Manager 6.5.21 release notes and 2024.5 release notes for any known issues and breaking changes relevant to your implementation.
  3. 3. Test the upgrade in a non-production environment first to ensure compatibility with your custom code, integrations, and third-party dependencies.
  4. 4. Upgrade Adobe Experience Manager to version 6.5.21 (for 6.x line) OR to version 2024.5 (for the modern release line), depending on your current deployment path.
  5. 5. After upgrading, verify that the DOM-based XSS vulnerability is mitigated by testing the affected components mentioned in the security bulletin.
  6. 6. Deploy the tested upgrade to production environment.
  7. 7. Monitor the system logs and AEM instance for any post-upgrade issues or unexpected behavior.
Caveat Review release notes for your specific AEM version and custom implementations before upgrading; some configurations or deprecated APIs may require adjustments

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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