dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36176

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 stored Cross-Site Scripting (XSS) vulnerability that could be abused by an attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.

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 stored Cross-Site Scripting (XSS) vulnerability in form fields. Attackers can inject malicious JavaScript into form inputs, which persists in the system and executes when other users view the affected pages.

MitigationUpdate to Adobe Experience Manager 6.5.21 or later to obtain the security patch. Additionally, implement input validation and output encoding for all form fields as a defense-in-depth measure.

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 your Adobe Experience Manager version
    Navigate to the AEM Welcome page or access /system/console/configMgr and look for the version information. Alternatively, check the manifest file in the crx-quickstart folder or run: curl -s http://localhost:4502/libs/granite/core/content/login.html?charset=utf-8 | grep -i version
    Affected if The installed version is below 6.5.21 or below the 2024.5 release (for cloud/ondemand variants)
  2. Identify form components in use
    Search the AEM content repository for form components: use CRXDE Lite (accessible at /crx/de) and query for nodes of type 'cq:Component' containing 'form' in the path, or search for files containing <form> tags in /content or /apps directories
    Affected if Form components exist and accept user input in your content structure
  3. Review stored form field data for malicious payloads
    Query the repository for existing form submissions or user-generated content: in CRXDE Lite, search for nodes under /content that contain script tags (<script), javascript: URLs, or common XSS patterns like onload=, onerror=, onmouseover= in attribute values
    Affected if Any form submission data contains HTML script tags or JavaScript event handlers (onclick, onerror, onload, etc.)
  4. Audit form field input validation settings
    Check the form component's dialog configuration in /apps for existing input validation rules. Examine the granite:dataTypes node or any validation constraints defined on form input fields
    Affected if No input validation or sanitization rules are configured on form fields that accept user content

You are affected if your AEM version is below 6.5.21 (or below 2024.5) AND you have form components that accept user input without proper validation, as evidenced by the presence of unsanitized script tags or XSS payloads in stored form data.

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

Update to Adobe Experience Manager 6.5.21 or later to obtain the security patch. Additionally, implement input validation and output encoding for all form fields as a defense-in-depth measure.

Recommended fix High confidence

Adobe Experience Manager 6.5.21 (for 6.5.x branches) or Adobe Experience Manager 2024.5 (for 2024.x branches)

  1. Verify current Adobe Experience Manager version by accessing the AEM Web Console (Help > Version)
  2. Review the AEM 6.5.21 release notes at helpx.adobe.com for changes and compatibility considerations
  3. Plan upgrade during a maintenance window with proper backups
  4. For AEM 6.5.x installations: upgrade to version 6.5.21
  5. For AEM Cloud Service or 2024.x installations: upgrade to version 2024.5
  6. After upgrade, verify the XSS fix is applied by testing form field inputs
Caveat Review 6.5.21 release notes for any compatibility changes before upgrading production environments

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-36176 — 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-36176 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