dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26045

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 · high confidence

Adobe Experience Manager versions 6.5.19 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability. Attackers can inject malicious JavaScript into form fields, which persists in the system. When victims browse to pages containing these compromised fields, the malicious script executes in their browsers.

MitigationUpgrade to Adobe Experience Manager version 6.5.20 or later. Until the patch is applied, implement input validation on form fields and consider Content Security Policy headers to mitigate XSS execution.

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. Check AEM product version
    Navigate to the AEM Welcome page or access the system information via the Help menu. Alternatively, check the version.properties file in the crx-quickstart folder or use the JMX console to query the version. Compare the installed version number against the affected ranges: below 6.5.20.0 or below 2024.3.0.
    Affected if Installed version is 6.5.19.x or earlier, or between 2024.1.0 and 2024.2.x (any version below 6.5.20.0 or 2024.3.0)
  2. Identify exposed form inputs
    Review the AEM Forms implementation and identify form components that accept user input and store data in the repository. Check Adaptive Forms, Foundation Forms, or custom form components that persist submissions to AEM content nodes.
    Affected if Form fields exist that accept and store user-submitted data in AEM without server-side validation
  3. Inspect stored form data for malicious scripts
    Use CRXDE Lite (accessible at /crx/de) or the Query Builder API to search JCR content nodes under /content or /var for stored form submissions. Look for patterns like <script, javascript:, onerror=, onload=, or other XSS vectors in attribute values.
    Affected if Form submission nodes contain HTML script tags, JavaScript event handlers, or suspicious script URLs in field values
  4. Review Content Security Policy headers
    Check the Apache Sling or Dispatcher configuration (usually in httpd.conf or .htaccess) for CSP header definitions. Look for response headers including 'Content-Security-Policy' and evaluate if script-src directives restrict inline scripts.
    Affected if CSP headers are missing, not configured, or allow 'unsafe-inline' which would permit stored XSS to execute

You are affected if your AEM version is below 6.5.20.0 or below 2024.3.0 AND you have form fields that accept user input exposed in your environment.

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 to Adobe Experience Manager version 6.5.20 or later. Until the patch is applied, implement input validation on form fields and consider Content Security Policy headers to mitigate XSS execution.

Recommended fix High confidence

AEM 6.5.20.0 (for 6.5.x line) or AEM as a Cloud Service 2024.3.0 (for Cloud Service line)

  1. 1. Back up the current Adobe Experience Manager instance and all content repositories
  2. 2. Review the AEM 6.5.20 release notes (or 2024.3.0 for Cloud Service) to identify any compatibility considerations or breaking changes
  3. 3. Test the upgrade in a non-production (staging) environment first
  4. 4. For AEM 6.5.x on-premise/managed services: upgrade to version 6.5.20.0 or later
  5. 5. For AEM as a Cloud Service: upgrade to version 2024.3.0 or later
  6. 6. Verify the XSS vulnerability is resolved by testing the previously vulnerable form fields
  7. 7. Deploy the upgraded version to production
Caveat Standard minor version upgrade; review release notes for any regression in custom code or third-party integrations before deploying to production

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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