dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36154

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.20 and earlier allows attackers to inject malicious JavaScript into vulnerable form fields, which executes in victims' browsers when viewing the affected pages.

MitigationApply Adobe's security patch by upgrading to AEM version 6.5.21 or later, which addresses this 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 Adobe Experience Manager installation
    Locate AEM instances by checking for AEM-related processes, web applications, or checking common AEM port listeners (typically 4502/4503 for author/publish). Query your asset management or infrastructure inventory for AEM deployments.
    Affected if AEM is present in the environment
  2. Determine installed AEM version
    Access the AEM Welcome page or system console (e.g., /crx/packmgr/list.jsp, /system/console/status/productinfo) to view the installed version. Alternatively, check the JAR file name or version properties in the AEM installation directory.
    Affected if Version is 6.5.20 or earlier, or falls below version 2024.5
  3. Identify form components accepting user input
    Review AEM form implementations, adaptive forms, and custom form fields within the content repository (search under /apps or /content for form-related components). Identify which form fields persist user-submitted data without proper output encoding.
    Affected if Form fields that store user input exist and lack output encoding controls
  4. Check for existing XSS payloads in stored form data
    Query the AEM repository or database for existing stored form submissions. Search for patterns indicating script tags or JavaScript event handlers in form field values.
    Affected if Malicious script content is found stored in form submission data

Your environment is affected if Adobe Experience Manager versions 6.5.20 or earlier (or pre-2024.5) are running AND form components that accept and store user input are in use.

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

Apply Adobe's security patch by upgrading to AEM version 6.5.21 or later, which addresses this stored XSS vulnerability.

Recommended fix Moderate confidence

AEM 6.5.21+ (on-premise) or AEM as a Cloud Service 2024.5+

  1. 1. Identify your current Adobe Experience Manager version and deployment type (6.5.x on-premise or AEM as a Cloud Service)
  2. 2. For AEM 6.5.x on-premise: Plan upgrade to version 6.5.21 or later
  3. 3. For AEM as a Cloud Service: Plan upgrade to version 2024.5 or later
  4. 4. Review the Adobe Experience Manager release notes for your target version to understand new features and changes
  5. 5. Create a full backup of your AEM instance including repository, database, and configuration files
  6. 6. Test the upgrade in a non-production environment first to verify compatibility with custom code and integrations
  7. 7. Schedule a maintenance window and notify users of expected downtime
  8. 8. Execute the upgrade following Adobe's official documentation for your deployment type
Caveat Review AEM 6.5.21 release notes for potential compatibility impacts; custom components interacting with form fields may require testing

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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