dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26085

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 in form fields. Attackers can inject malicious JavaScript payloads into form inputs, which are then stored and executed when subsequent users view the affected page containing those vulnerable fields.

MitigationUpgrade Adobe Experience Manager to version 6.5.21 or later. Additionally, implement output encoding and input validation on form fields to prevent script injection.

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. Determine Adobe Experience Manager version
    Access the AEM Welcome page or check the product version through the system console (typically at /system/console/config or by reviewing the version.txt in the installation directory). Compare against affected versions: any AEM installation running version 6.5.20 or earlier, or any version prior to the 2024.5 release.
    Affected if The installed version is 6.5.20 or earlier, or the version is below 2024.5 (for cloud/continuous releases).
  2. Identify form field usage in the environment
    Review the AEM instance for custom or third-party form components. Check the /apps and /libs directories for custom form field components, especially in content fragments, adaptive forms, or custom-developed form implementations.
    Affected if Custom form components or third-party form implementations are installed and in use on the AEM instance.
  3. Inspect form data storage for suspicious payloads
    Query the AEM repository (JCR) or examine stored form submission data for any JavaScript tags, script elements, or event handlers (onerror, onload, onclick, etc.) that may have been injected into form fields.
    Affected if Stored form data contains unsanitized JavaScript code or HTML tags that could be executed when viewed by other users.
  4. Review content pages containing forms
    Access pages that host form components and inspect the page source or rendered output to verify if input validation and output encoding are properly applied to all form fields.
    Affected if Form fields render user-supplied input without proper output encoding, allowing script execution.

You are affected if your AEM version is 6.5.20 or earlier (or pre-2024.5 for continuous releases) AND custom form fields are in use without proper input validation and output encoding.

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. Additionally, implement output encoding and input validation on form fields to prevent script injection.

Recommended fix High confidence

Adobe Experience Manager 6.5.21 or newer, or 2024.5 or newer (depending on your release track)

  1. Identify your current Adobe Experience Manager version (6.5.x or 2024.x release line)
  2. For AEM 6.5.x line: Upgrade to AEM 6.5.21 or later
  3. For AEM 2024 release line: Upgrade to 2024.5 or later
  4. After upgrade, verify the XSS protection is working by testing form fields that accept user input
  5. Ensure custom code that may have workarounds for the vulnerability is reviewed and updated to rely on the built-in fix

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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