dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36174

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.20 and earlier allows attackers to inject malicious JavaScript into form fields, which persists and executes when other users view pages containing the affected fields.

MitigationUpgrade Adobe Experience Manager to version 6.5.21 or later, or apply the appropriate security patch to remediate the stored XSS vulnerability.

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 Adobe Experience Manager version
    Access the AEM welcome page or use the system console (help -> About Adobe Experience Manager) to view the product version. Alternatively, check the quickstart folder for the version manifest file.
    Affected if The version displayed is 6.5.20 or earlier, or any version prior to the 2024.5 release.
  2. Determine if the AEM Forms module is in use
    Check if the AEM Forms add-on package is installed by navigating to Package Manager or reviewing the installed bundles related to forms functionality.
    Affected if The Forms module is installed and active on the instance.
  3. Review custom form field configurations
    Inspect the form component configurations in the CRX/DE repository (under /apps or /content) to identify custom form fields that accept user input without proper server-side validation.
    Affected if Custom form field definitions exist that allow unsanitized input storage.
  4. Audit existing form content for suspicious scripts
    Query the repository (using Query Builder or Groovy) for stored form submissions containing script tags in field values. Look for patterns like <script> or javascript: in form data.
    Affected if Form data entries contain unsanitized script tags or event handler attributes.

The environment is likely affected if the installed AEM version is below 6.5.21 or below 2024.5 AND the system uses form components that accept and persist user input without server-side validation.

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 Adobe Experience Manager to version 6.5.21 or later, or apply the appropriate security patch to remediate the stored XSS vulnerability.

Recommended fix High confidence

AEM 6.5.21 or later / AEM 2024.5 or later

  1. Identify the current Adobe Experience Manager version in use
  2. Navigate to the Adobe Software Distribution portal or use Package Manager to obtain the fixed release
  3. For AEM 6.5.x: Upgrade to version 6.5.21 or later
  4. For AEM as a Cloud Service: Upgrade to version 2024.5 or later
  5. Deploy the upgraded version to your environment following standard AEM deployment procedures
  6. Verify the upgrade was successful by checking the AEM version in the About Adobe Experience Manager console
  7. Clear the AEM cache and republished content to ensure no cached malicious scripts remain
Caveat Review AEM 6.5.21 and 2024.5 release notes for potential compatibility or configuration changes before upgrading

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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