dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36196

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. Attackers can inject malicious JavaScript into form fields, which persists in the system and executes when legitimate users browse to pages containing the compromised fields.

MitigationUpgrade Adobe Experience Manager to version 6.5.21 or later to obtain the security patch. Additionally, implement input validation and output encoding on 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. Identify Adobe Experience Manager version
    Access the AEM Welcome page or check the product version through the system console at /system/console/status-productinfo, or run: java -jar cq-quickstart-*.jar -version
    Affected if The installed version is 6.5.20 or earlier, or falls below 2024.5 for the 2024 release line
  2. Determine if custom form components are deployed
    Review the /apps directory in CRX/DE (accessible at /crx/de) or look for custom form field components in the content structure under /content that use Granite UI Form or Core Components forms
    Affected if Custom form components or adaptive forms that accept user input are present in the system
  3. Audit stored form submissions for malicious payloads
    Query the content repository using CRXDE or a JCR search tool for suspicious script tags in form field nodes, for example searching for <script or javascript: in nodes under /content that contain form data
    Affected if Any stored form submissions contain unsanitized script tags or event handler attributes
  4. Check if forms allow HTML/rich text input
    Review form field configurations in the AEM Forms UI or examine the XML schema/JSON model for text fields to see if allowRichText or similar options are enabled without output encoding
    Affected if Form fields are configured to accept rich HTML content or have input validation disabled

You are affected if your AEM version is below 6.5.21 (or 2024.5) AND you have custom form fields that accept and store user input without proper sanitization.

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 to obtain the security patch. Additionally, implement input validation and output encoding on form fields as a defense-in-depth measure.

Recommended fix Moderate confidence

AEM 6.5.21 (for 6.x on-premise) or 2024.5.1 (for Cloud Service)

  1. 1. Back up your current AEM instance including repository, database, and configurations
  2. 2. Review the Adobe Experience Manager 6.5.21 or 2024.5.1 upgrade documentation for your specific deployment type
  3. 3. Test the upgrade in a non-production environment first to validate compatibility
  4. 4. Schedule a maintenance window for the production upgrade
  5. 5. Upgrade Adobe Experience Manager to version 6.5.21 (for 6.x customers) or version 2024.5.1 (for Cloud Service customers)
  6. 6. After upgrade, verify the XSS fix is applied by testing the previously vulnerable form fields
  7. 7. Monitor system logs and user sessions for any anomalies post-upgrade
Caveat Standard AEM upgrade risks apply - review custom code, third-party integrations, and ensure compatibility with the target version before production deployment

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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