dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26114

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 reflected Cross-Site Scripting (XSS) vulnerability. If an attacker is able to convince a victim to visit a URL referencing a vulnerable page, malicious JavaScript content may be executed within the context of the victim's browser.

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 reflected Cross-Site Scripting (XSS) vulnerability where malicious JavaScript can be injected via URLs and executed within the victim's browser context when they visit a crafted link.

MitigationUpgrade Adobe Experience Manager to a version after 6.5.20, or implement input validation and output encoding on vulnerable parameters along with Content Security Policy headers to mitigate XSS attacks.

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 installed AEM version
    Navigate to the AEM welcome page or version information page (typically at /libs/granite/ui/content/shell/console/about.html or check the footer of the AEM start page). The version number is displayed on the welcome screen or about page.
    Affected if The displayed version is lower than 6.5.21 or lower than 2024.5 (for cloud/2024 releases).
  2. Verify version via system console
    Access /system/console/bundles and locate the Adobe Experience Manager Core bundle, or access /system/console/productinfo to view the complete product version information.
    Affected if The version returned is earlier than 6.5.21 or earlier than 2024.5.
  3. Check AEM package manager version
    Access the Adobe Package Manager (via /crx/packmgr/list.jsp?verb=show) or check the installed service packs listed in the AEM updates section.
    Affected if The installed service packs or cumulative fixes are earlier than the 6.5.21 or 2024.5 releases.
  4. Confirm affected release track
    Determine if the deployment is on the 6.5 (on-premise) release track or the 2024 (cloud/managed services) release track by checking the product version string format.
    Affected if The version starts with 6.x and is below 6.5.21, OR the version is in the 2024.x format and is below 2024.5.

Your environment is affected if the installed Adobe Experience Manager version is below 6.5.21 on the 6.5 release track, or below 2024.5 on the 2024 release track.

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 a version after 6.5.20, or implement input validation and output encoding on vulnerable parameters along with Content Security Policy headers to mitigate XSS attacks.

Recommended fix High confidence

AEM 6.5.21 or AEM 2024.5 (depending on your release line)

  1. 1. Back up your current Adobe Experience Manager instance and verify backup integrity
  2. 2. Review Adobe's official release notes for the target version to understand changes
  3. 3. Download Adobe Experience Manager 6.5.21 (or 2024.5 if using the newer release line) from the official Adobe distribution portal
  4. 4. Test the upgrade in a non-production environment first
  5. 5. Deploy the upgraded version to production after validation

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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