dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36190

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 user 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

DOM-based Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.20 and earlier. The vulnerability allows execution of arbitrary JavaScript code in the context of a victim's browser session through malicious input that gets reflected in the DOM without proper sanitization.

MitigationImplement proper input validation and output encoding in client-side JavaScript to sanitize data before rendering to the DOM; consider Content Security Policy (CSP) headers as defense-in-depth.

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. Identify AEM installation version
    Access the AEM System Information console at /system/console/status-html or locate the version.properties file in the crx-quickstart folder to determine the installed version number
    Affected if The version shown is 6.5.20 or earlier, or falls below version 2024.5
  2. Confirm version is within affected range
    Compare the discovered version against the vulnerable ranges: versions below 6.5.21 (for 6.x releases) or versions below 2024.5 (for yearly releases) are affected
    Affected if The installed version is less than 6.5.21 or less than 2024.5
  3. Identify custom or third-party components with client-side rendering
    Review the /apps and /libs directories for custom components, especially those usingGranite UI, Coral UI, or any custom client-side JavaScript that processes and renders user input to the browser DOM
    Affected if Custom components exist that accept user input and render it directly to the DOM without server-side sanitization
  4. Audit client-side JavaScript for unsafe DOM operations
    Examine custom clientlib JavaScript files (typically in /apps/*/clientlibs) for patterns like innerHTML赋值, document.write(), or similar DOM manipulation methods that process request parameters, form input, or URL fragments
    Affected if Custom JavaScript code uses unescaped data from request parameters, form fields, or URL fragments in DOM operations
  5. Check for unvalidated input reflection points
    Inspect any client-side code that reads query parameters, path selectors, or fragment identifiers and inserts that data into page elements using selectors like document.getElementById or jQuery methods
    Affected if User-controllable data from URL or forms is reflected into the DOM without encoding or validation

Your environment is affected if running AEM version 6.5.20 or earlier, or version 2024.4 or earlier, AND custom components or client-side scripts reflect unsanitized user input into the DOM.

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

Implement proper input validation and output encoding in client-side JavaScript to sanitize data before rendering to the DOM; consider Content Security Policy (CSP) headers as defense-in-depth.

Recommended fix High confidence

AEM 6.5.21 or later (6.5.x branch) / AEM as a Cloud Service 2024.5 or later

  1. 1. Back up your current Adobe Experience Manager instance and database before proceeding with any upgrade.
  2. 2. Review the Adobe Experience Manager upgrade documentation for your current version to the target version.
  3. 3. Download Adobe Experience Manager 6.5.21 (or later 6.5.x version) from the Adobe Distribution Software Package (DSP) or your licensed distribution channel.
  4. 4. Install the upgrade following the standard AEM upgrade procedure: stop the AEM instance, run the upgrade installer, verify the migration, and restart the instance.
  5. 5. After upgrade, verify that the AEM instance starts successfully and all custom bundles are functioning.
  6. 6. Test the specific functionality that could be affected by the XSS fix to ensure proper operation.
  7. 7. Clear browser caches and test that the DOM-based XSS vulnerability is no longer exploitable.
Caveat Review Adobe's 6.5.21 release notes for any compatibility notices; AEM upgrades may require updates to custom code or configurations

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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