dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26031

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-18
Fix available
A fix is available. Upgrade to 6.5.20.0 / 2024.3.0 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.19 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

Adobe Experience Manager versions 6.5.19 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability allowing attackers to inject malicious JavaScript into form fields. When victims browse to pages containing these compromised fields, the injected scripts execute in their browsers, potentially enabling session hijacking or data theft.

MitigationUpgrade Adobe Experience Manager to version 6.5.20 or later. Until patched, implement strict input validation and output encoding on all form fields, and consider Content Security Policy headers as defense-in-depth.

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.20.0< 2024.3.0

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 installed AEM version
    Access the AEM Web Console (about:admin) or check the package manager for the com.adobe.aemforms product version, or query the OSGi bundle version at /system/console/bundles
    Affected if The installed version is below 6.5.20.0 or below 2024.3.0 (for cloud/2024 releases)
  2. Identify exposed form components
    Review the AEM content structure under /content for pages using Core Components form containers (core/wcm/components/form/...) or Adaptive Forms that accept user input without explicit server-side validation
    Affected if Form components that accept user input are published and accessible to unauthenticated or low-privileged users
  3. Inspect form field configurations for input validation
    Open the form component dialog in Edit mode (http://localhost:4502/editor.html/path/to/form) and verify if the 'Use Inline Validation' or 'Constraint' settings are configured, then check if custom validation rules exist at /apps or /libs
    Affected if Form fields lack server-side validation constraints or rely solely on client-side validation
  4. Review Content Security Policy headers
    Run a curl -I against published AEM pages to inspect response headers for CSP headers (Content-Security-Policy, X-Content-Security-Policy)
    Affected if No CSP headers are set, or CSP headers do not include 'script-src' restrictions that would block inline scripts

A user is affected if their AEM version is below 6.5.20.0 or below 2024.3.0 AND they have published form components accessible to users without strict server-side input validation and without CSP headers blocking inline scripts.

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.20.0 / 2024.3.0 or later
Fixed in 6.5.20.02024.3.0
Interim mitigation

Upgrade Adobe Experience Manager to version 6.5.20 or later. Until patched, implement strict input validation and output encoding on all form fields, and consider Content Security Policy headers as defense-in-depth.

Recommended fix High confidence

AEM 6.5.20.0+ or AEM as a Cloud Service 2024.3.0+

  1. Verify current Adobe Experience Manager version by accessing /system/console/bundles or checking the AEM welcome page
  2. Review the AEM upgrade planning documentation for your current version
  3. Create a full backup of the AEM repository (crx-quickstart) and database before proceeding
  4. Test the upgrade in a staging environment before applying to production
  5. Upgrade AEM 6.5.x installations to version 6.5.20.0 or later
  6. For AEM as a Cloud Service, ensure the deployment uses version 2024.3.0 or later
  7. After upgrade, verify that the XSS protection filters are functioning correctly by testing form field inputs with script tags
  8. Clear AEM caches and rebuild indexes as part of standard post-upgrade procedures
Caveat Standard AEM upgrade considerations apply - review deprecated APIs and custom code compatibility

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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