dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26060

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 where malicious JavaScript can be injected into form fields and persists in the system. When victims browse to pages containing these compromised form fields, the malicious scripts execute in their browsers.

MitigationUpgrade Adobe Experience Manager to version 6.5.21 or later to obtain the security patch. Additionally, audit custom form components for proper input sanitization and output encoding.

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. Check the installed Adobe Experience Manager version
    Navigate to the AEM welcome page or check the version via the system information console (typically at /system/console/bundles or /crx/packmgr/version.jsp). Locate the AEM version number displayed.
    Affected if The version is earlier than 6.5.21 or earlier than the 2024.5 release (for Cloud Service/2024 releases).
  2. Identify if Forms or custom form components are in use
    Review the AEM instance for any deployed custom form components or adaptive forms. Check the /apps or /content directories for components containing 'form' in their node names, or review the Forms UI at /aem/forms.
    Affected if Custom form components or adaptive forms are deployed and actively used on the instance.
  3. Inspect form field content for unsanitized input
    Access the AEM repository via CRX/DE (at /crx/de) and search for form-related content nodes under /content that contain user-submitted data in form fields. Look for any content in form components that may contain script tags or javascript: URLs.
    Affected if Any form submissions or form-based content nodes contain raw, unsanitized HTML or script tags in text fields.
  4. Review recent form submission logs or content
    Check the AEM Forms service logs and any database or repository storing form submissions. Look for entries containing <script>, javascript:, or other HTML tags in input fields.
    Affected if Form submission logs or stored content contains HTML tags, script elements, or JavaScript event handlers that were not encoded or sanitized upon storage.

A user is affected if their AEM version is below 6.5.21 (or below 2024.5 for newer releases) AND they have forms or custom form components 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, audit custom form components for proper input sanitization and output encoding.

Recommended fix High confidence

AEM 6.5.21 (for 6.5.x branch) or 2024.5 release (for AEM as a Cloud Service)

  1. 1. Back up your current Adobe Experience Manager instance and database before attempting any upgrade.
  2. 2. Review the Adobe Experience Manager 6.5.21 release notes at helpx.adobe.com for any specific migration or compatibility requirements.
  3. 3. For AEM 6.5.x users: Upgrade to version 6.5.21 or later by following the standard AEM upgrade documentation.
  4. 4. For AEM as a Cloud Service users: Ensure your environment is updated to the 2024.5 release or later through the Cloud Manager pipeline.
  5. 5. After upgrade, verify that all custom form components properly sanitize user input to prevent XSS vulnerabilities.
  6. 6. Test the upgraded environment thoroughly, particularly any form-based workflows that handle user-submitted content.
Caveat Review 6.5.21 release notes for potential compatibility changes; standard upgrade risks apply including custom code compatibility and dependency updates

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
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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