dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36210

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 reflected Cross-Site Scripting (XSS) vulnerability. If an attacker is able to convince a victim to visit a URL referencing a vulnerable page, malicious JavaScript content may be executed within the context of the victim's browser.

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 · moderate confidence

Adobe Experience Manager versions 6.5.20 and earlier contain a reflected XSS vulnerability where user-supplied input in a URL parameter is insufficiently sanitized and reflected back to the victim's browser, allowing arbitrary JavaScript execution within the context of the vulnerable page.

MitigationUpgrade to AEM 6.5.21 or later to obtain the vendor patch; until then, implement URL parameter validation and output encoding on affected endpoints, and train users to avoid clicking untrusted links.

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 the installed AEM version
    Access the AEM Developer Console or check the version.properties file in the crx-quickstart folder. Alternatively, navigate to the AEM Welcome page and locate the version information in the 'Product Information' section or use the /system/console/bundles endpoint to confirm the AEM core bundle version.
    Affected if The installed version is earlier than 6.5.21 or earlier than the 2024.5 release.
  2. Verify URL parameter handling on custom endpoints
    Review any custom Sling servlets, JSP files, or Sightly templates that process query string parameters via request.getParameter() and directly output them to the response without applying server-side encoding.
    Affected if Custom code accepts URL parameters and reflects them unencoded in the HTML response.
  3. Audit published pages for unvalidated parameter reflection
    Test published AEM pages by appending a test parameter such as ?test=<script>alert(1)</script> to the URL and inspecting whether the raw script tags appear in the page source without HTML encoding.
    Affected if The parameter value is reflected verbatim in the rendered HTML without server-side output encoding.
  4. Check for disabled XSS protection filters
    Inspect the OSGi configuration for the Adobe CSRF Filter and XSS API configurations in the AEM Web Console at /system/console/configMgr. Verify whether custom XSS rules have relaxed protection on the affected endpoints.
    Affected if XSS filtering is disabled or custom rules allow unencoded parameter output on the affected endpoint.

A user is affected if their AEM installation is version 6.5.20 or earlier (or earlier than 2024.5) AND they have custom code or endpoints that reflect URL parameters without proper output encoding.

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 obtain the vendor patch; until then, implement URL parameter validation and output encoding on affected endpoints, and train users to avoid clicking untrusted links.

Recommended fix High confidence

Adobe Experience Manager 6.5.21 (on-premises) or AEM as a Cloud Service 2024.5 and later

  1. 1. Identify the current Adobe Experience Manager version by checking the product about page or system console
  2. 2. For AEM 6.5.x installations: Upgrade to version 6.5.21 or later
  3. 3. For AEM as a Cloud Service: Upgrade to version 2024.5 or later
  4. 4. After upgrade, verify the XSS vulnerability is remediated by reviewing release notes and testing
  5. 5. Ensure standard regression testing is performed to confirm no functionality was impacted
Caveat No breaking changes expected; this is a security patch release within the same major version

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 / QA3.0 h
19.0 hours of engineering $3,380
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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