dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36192

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 · moderate 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 users view pages containing the compromised fields.

MitigationUpgrade Adobe Experience Manager to version 6.5.21 or later to obtain the security patch. Additionally, implement output encoding and content security policy headers as defense-in-depth measures.

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 installation
    Check for AEM by looking for common installation paths (e.g., /opt/aem, /crx) or accessing the AEM Welcome page at /aem/start.html or the login page at /libs/granite/core/content/login.html
    Affected if AEM is present and accessible via typical AEM URLs or directories like crx-quickstart exist on the server
  2. Determine installed AEM version
    Access the AEM Version page at /system/console/bundles or check the product info via the AEM Web Console at /system/console/product.json, or examine the version.txt file in the crx-quickstart folder
    Affected if The detected version is below 6.5.21 or below 2024.5
  3. Identify custom form components accepting user input
    Review custom form components in the /apps directory that accept user input in text fields, textareas, or other data capture elements where values could be stored in the repository
    Affected if Custom form components exist that store user-submitted data without explicit output encoding
  4. Check if form field data is rendered on published pages
    Examine how form field values are rendered in content pages or content fragments by reviewing the HTL, JSP, or Sightly templates responsible for displaying stored form data
    Affected if Form field data from user inputs can be rendered on pages without visible encoding or sanitization in the display templates

Your environment is affected if Adobe Experience Manager version is below 6.5.21 (or below 2024.5) and custom form components that persist user input are in use, allowing stored malicious scripts to execute when other users view the compromised content.

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 output encoding and content security policy headers as defense-in-depth measures.

Recommended fix High confidence

AEM 6.5.21 (for 6.5.x line) or AEM 2024.5 (for cloud/continuous release)

  1. 1. Back up your current Adobe Experience Manager instance, including the repository, database, and configuration files
  2. 2. Download Adobe Experience Manager 6.5.21 (for on-premise 6.5.x customers) or the 2024.5 release (for cloud/continuous release customers) from the official Adobe distribution portal
  3. 3. Set up a staging or development environment that mirrors your production configuration
  4. 4. Apply the upgrade to the staging environment and run comprehensive testing, including verifying that forms with user input properly sanitize malicious scripts
  5. 5. Schedule a maintenance window for production deployment
  6. 6. Apply the upgrade to production environment
  7. 7. Verify the fix by attempting to inject a test XSS payload into vulnerable form fields and confirming it is neutralized
  8. 8. Clear AEM caches and rebuild any search indexes if necessary
Caveat Standard upgrade precautions apply - test thoroughly in non-production first, as custom code or third-party integrations may require adjustments

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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