CVE-2024-26040
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 · uneditedAdobe 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 confidenceAdobe 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 and executes when users view pages containing the compromised fields.
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< 6.5.20.0< 2024.3.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine your Adobe Experience Manager versionAccess the AEM Welcome page or use the versioninfo endpoint to retrieve the installed product version. In the AEM main menu, navigate to Tools > Operations > Web Console, or append /system/console/configMgr to your instance URL, then locate the Product Information panel showing the version number.Affected if The installed version is below 6.5.20.0 or below 2024.3.0 (for cloud/managed services). Versions prior to these thresholds are affected by the stored XSS vulnerability.
-
Identify use of AEM Forms or form-based componentsReview your AEM instance for any deployed Adaptive Forms, Foundation Forms, or custom form components that accept user-submitted data. Check the Forms section in AEM Assets or the Forms Manager at /aem/forms if available.Affected if The vulnerability specifically targets form fields where malicious scripts can be injected and persisted. If forms are in use and the AEM version is below the fixed releases, the environment is potentially affected.
-
Inspect form submission data for injected scriptsQuery the content repository or form data storage for entries containing script tags, javascript: URIs, or event handler attributes (onload, onerror, onclick, etc.) within form field values. Use CRX/DE at /crx/de or the Query Builder if accessible.Affected if Form submission records contain executable script content that was successfully injected, indicating active exploitation of the stored XSS flaw.
-
Review published pages rendering form contentExamine published pages that display form data to confirm whether submitted values are being rendered without proper output encoding. Inspect the HTML source of rendered form fields.Affected if Form field values are rendered as raw HTML or with event handlers intact rather than being escaped, confirming the XSS vulnerability is present in the rendered output.
-
Check audit logs and access logs for XSS probe patternsReview AEM request logs and the audit log for suspicious patterns such as <script>, javascript:, or HTML tag injection attempts in form submission parameters.Affected if Recent or historical requests contain XSS injection attempts targeting form endpoints, suggesting the vulnerability has been targeted.
Your environment is affected if Adobe Experience Manager is installed at a version below 6.5.20.0 (on-prem) or below 2024.3.0 (cloud/managed services) AND the instance uses AEM Forms or form components where user input is stored and rendered back without sanitization.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.5.20.02024.3.0
Update Adobe Experience Manager to version 6.5.20 or later to apply the security patch. Additionally, review and sanitize existing form submissions to remove any injected malicious scripts.
AEM 6.5.20.0 (for 6.5.x line) or AEM 2024.3.0 (for newer releases)
- 1. Review the Adobe Experience Manager upgrade documentation for your current version
- 2. Perform a full backup of your AEM instance and content repository
- 3. Test the upgrade in a non-production environment first
- 4. Upgrade AEM 6.5.x installations to version 6.5.20.0 or later
- 5. For newer AEM releases, upgrade to version 2024.3.0 or later
- 6. After upgrade, verify the XSS fix is properly applied by testing form fields for proper input sanitization
- 7. Deploy to production after successful validation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26040 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-26040 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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