dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26123

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 form fields. The injected payload persists in the system and executes in victim browsers when they view pages containing the compromised form fields.

MitigationUpdate Adobe Experience Manager to version 6.5.21 or later to apply the vendor patch. Additionally, implement input validation and output encoding on form fields as a defense-in-depth measure.

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
    Access the AEM System Information console at /system/console/status-AEMProductInfo or check the pom.xml for the artifact com.adobe.aem:uber-jar version
    Affected if The installed version is 6.5.20 or earlier, or the version is before 2024.5 (for example, 6.5.x where x < 21, or any release prior to the 2024.5 release)
  2. Confirm AEM Forms module is in use
    Navigate to /libs/fd/fm/view/forms/index.html or check the AEM Package Manager for com.adobe.aemfd packages installed
    Affected if AEM Forms or Adaptive Forms functionality is enabled and users can create or edit form fields
  3. Examine stored form data for unsanitized input
    Query the AEM JCR repository at /content/forms/af or use CRXDE Lite to inspect form field node properties under /content/forms/af/<form-name> for any script tags or javascript: URIs in field values
    Affected if Form field nodes contain raw, unescaped HTML or script tags stored in the repository without sanitization
  4. Inspect form field validation configuration
    Check form field component XML configs under /apps or /libs (for example, core/wcm/components/form/text/v2/text) for missing or disabled server-side input validation rules
    Affected if Form field components lack server-side validation rules or have validation explicitly disabled (validation="disabled")
  5. Review AEM Content Security Policy headers
    Access the Apache Sling Main Servlet configuration at /system/console/config/org.apache.sling.security.impl.ContentSecurityFilter and check the script-src directive
    Affected if The Content Security Policy does not include 'unsafe-inline' restrictions or is not configured to block inline script execution

You are affected if your AEM version is 6.5.20 or earlier OR any version prior to 2024.5, AND you have AEM Forms enabled with form fields that accept user input without server-side 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

Update Adobe Experience Manager to version 6.5.21 or later to apply the vendor patch. Additionally, implement input validation and output encoding on form fields as a defense-in-depth measure.

Recommended fix High confidence

Adobe Experience Manager 6.5.21 or later, or 2024.5 or later

  1. Backup your current Adobe Experience Manager instance and database
  2. Review the Adobe Experience Manager 6.5.21 (or 2024.5) release notes for any known issues or migration requirements
  3. Test the upgrade in a non-production environment before deploying to production
  4. Upgrade Adobe Experience Manager to version 6.5.21 or later (for 6.5.x releases) OR to version 2024.5 or later (for 2024 releases)
  5. Verify that the stored XSS vulnerability is resolved by testing form field inputs with malicious scripts
  6. Deploy the upgraded instance to production after successful validation
Caveat Review release notes for any migration steps or configuration changes required; major version upgrades may have breaking changes in APIs or custom code

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 / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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