dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26058

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 Answer: are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability. This vulnerability could allow an attacker to execute arbitrary JavaScript code in the context of the victim's browser session. Exploitation of this issue requires user interaction, such as convincing a victim to click on a specially crafted link.

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 DOM-based Cross-Site Scripting (XSS) vulnerability. The flaw allows execution of arbitrary JavaScript in a victim's browser when they interact with a specially crafted link, enabling session hijacking or other client-side attacks.

MitigationUpgrade Adobe Experience Manager to version 6.5.21 or later to obtain the vendor patch. Users should be advised to avoid clicking untrusted links as a compensating control until the upgrade is applied.

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. Locate the Adobe Experience Manager version number
    Access the AEM welcome page and scroll to the footer, or navigate to /system/console/config and locate the version information banner. The version is also visible in the filename of the crx-quickstart folder or in the version.properties file within that folder.
    Affected if The displayed version is 6.5.20 or earlier, or any version below 2024.5 for the yearly release track.
  2. Confirm the AEM instance is running and accessible
    Verify the AEM author or publish instance is accessible via HTTP/HTTPS. The vulnerability requires an active, reachable instance for the XSS to be triggered through user interaction with a crafted link.
    Affected if The instance is running and network-accessible, which is the typical default configuration.
  3. Identify if the vulnerable component is exposed
    This DOM-based XSS is triggered through specially crafted links to AEM pages. Determine if external users or internal users can access AEM URLs directly, as the attack requires a victim to click a malicious link.
    Affected if AEM pages are accessible to users who could potentially click untrusted links, which is the standard usage pattern.

You are affected if your AEM version is 6.5.20 or earlier, or below 2024.5, and the instance is accessible for users to interact with crafted URLs.

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 vendor patch. Users should be advised to avoid clicking untrusted links as a compensating control until the upgrade is applied.

Recommended fix Moderate confidence

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

  1. 1. Identify your current Adobe Experience Manager deployment type (on-premise/cloud) and version
  2. 2. For AEM on-premise (6.5.x): Upgrade to version 6.5.21 or later
  3. 3. For AEM as a Cloud Service: Upgrade to version 2024.5 or later
  4. 4. After upgrade, verify the XSS vulnerability is resolved by testing with the originally reported payload or similar DOM-based XSS vectors
  5. 5. Clear any cached content and rebuild any custom indexes if applicable

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 / QA4.0 h
40.0 hours of engineering $7,000
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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