CVE-2024-26110
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.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 confidenceAdobe Experience Manager versions 6.5.20 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability. Attackers can inject malicious JavaScript into vulnerable form fields, which persists on the page. When victims browse to pages containing these compromised fields, the malicious scripts execute in their browsers.
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.21< 2024.5CVSS 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.
-
Identify Adobe Experience Manager installation and versionLocate the AEM installation and determine the installed version. Common locations include /opt/aem, /crx-quickstart, or custom install paths. Check for version files like 'manifest.xml' in crx-quickstart or use the AEM Web Console (system/console/systeminfo) which displays the product version.Affected if The installed version is 6.5.20 or earlier, or any version prior to 2024.5 (for newer release trains), placing it within the vulnerable version range.
-
Confirm AEM Forms or custom form components are in useReview the AEM instance for any deployed form components, Adaptive Forms, or custom form implementations. Check the CRX/DE Lite (/crx/de) or Package Manager for form-related packages or content structures under /content/forms.Affected if The AEM instance uses Forms functionality or contains custom form fields that accept and store user input, creating the attack surface for stored XSS.
-
Check if form submissions can be created by unauthenticated or low-privileged usersExamine the permission model for form submission endpoints and form creation workflows. Determine if anonymous users or standard authors can submit or edit form content. Review ACLs and replication settings for form-related content paths.Affected if Users with limited privileges (especially unauthenticated users) can submit or modify form field data that gets stored and displayed without sanitization.
-
Inspect form field input handling and output encodingReview the form components' JSP, HTL, or JavaScript renderer files for how form inputs are handled. Look for whether user-supplied values are properly escaped or sanitized before rendering. Check for proper use of XSS API utilities in component code.Affected if Form field values are rendered without proper HTML encoding or XSS sanitization, allowing injected JavaScript to persist and execute.
-
Verify stored form data is rendered in the vulnerable mannerSubmit a test form entry containing a benign script payload (such as <script>alert('test')</script>) in a form field, then navigate to the page where that data is displayed to confirm if the script executes.Affected if The injected script payload executes when viewing pages that display the stored form data, confirming the XSS vulnerability is present and exploitable.
You are affected if your AEM installation version is 6.5.20 or earlier (or below 2024.5 for newer release trains) AND your instance uses form functionality where untrusted input can be stored and displayed without proper output encoding.
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.212024.5
Apply Adobe Experience Manager security patch 6.5.21 or later to address this vulnerability. Validate and sanitize all form field inputs as an additional defense-in-depth measure.
Adobe Experience Manager 6.5.21 or later (6.5.x line); Adobe Experience Manager 2024.5 or later (2024.x line)
- 1. Identify current Adobe Experience Manager version by checking the AEM Welcome page or system console
- 2. If running AEM 6.5.x line, plan upgrade to version 6.5.21 or later
- 3. If running AEM 2024.x line, plan upgrade to version 2024.5 or later
- 4. Create a full backup of the AEM instance including repository, database, and configuration files
- 5. Review Adobe's official upgrade documentation and release notes for the target version
- 6. Test the upgrade in a non-production environment first
- 7. Schedule maintenance window and stop the AEM instance
- 8. Run the upgrade following Adobe's recommended upgrade procedure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26110 — 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-26110 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