CVE-2024-26054
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 · moderate confidenceAdobe Experience Manager versions 6.5.20 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. Attackers can inject malicious JavaScript that persists in the system and executes when users view pages containing the compromised form fields, leading to session hijacking or credential theft.
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.
-
Verify AEM version is vulnerableAccess the AEM Welcome page and navigate to Help > Version Information, or check the version.properties file in the crx-quickstart directory. Compare the version number to the affected ranges: version 6.5.20 or earlier, or any version prior to 2024.5.Affected if The installed version is 6.5.20 or earlier, or the version is before 2024.5 (for the cloud/managed services release).
-
Identify form fields accepting user inputReview the AEM instance for Adaptive Forms, Form Containers, or core form components (text fields, textareas, number fields) that accept user-submitted content. Check in the Forms section of AEM Assets or through the component finder.Affected if Adaptive Forms or form components that allow direct user input are present and active on the instance.
-
Inspect stored form field data for malicious scriptsQuery the AEM repository (via CRXDE Lite or the Query Builder) for form field content containing script tags, javascript: URIs, or event handlers like onload, onerror. Navigate to /content and search across form submission nodes.Affected if Any form field data entries contain HTML script tags, JavaScript event handlers, or encoded XSS payloads.
-
Review published pages rendering formsAccess published pages that display forms and view the page source. Check if form field values are rendered without proper output encoding, allowing stored scripts to execute in user browsers.Affected if Form values rendered on pages execute JavaScript or display unescaped HTML content from user input.
A user is affected if their AEM version is below 6.5.21 (or pre-2024.5 for cloud) AND they have form fields accepting user input that contain or render malicious script content 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.212024.5
Upgrade Adobe Experience Manager to version 6.5.21 or later to obtain the security patch. Additionally, implement input validation and output encoding on form fields, and configure Content Security Policy (CSP) headers as a defense-in-depth measure.
Adobe Experience Manager 6.5.21 (for 6.5.x line) or 2024.5 (for 2024.x release train)
- Review Adobe Experience Manager 6.5.21 (or 2024.5 for newer release train) release notes for changes and prerequisites
- Create a full backup of the AEM instance including repository, database, and configurations
- Set up a staging or development environment identical to production
- Test the upgrade in the staging environment to identify any compatibility issues
- Execute the upgrade following Adobe's official upgrade documentation (typically using the Upgrade Procedure or CRX Package Manager)
- After upgrade, verify that the XSS protection fixes are applied by testing form field inputs with malicious scripts
- Confirm all custom code, workflows, and integrations function correctly in the upgraded environment
- Deploy to production after successful validation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26054 — 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-26054 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