CVE-2024-26096
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.19 and earlier allows authenticated attackers to inject malicious JavaScript into form fields. The malicious payload persists in the system and executes when other users view pages containing the compromised form 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.
-
Identify installed AEM versionAccess the AEM System Information console at /system/console/status-productinfo or check the version.properties file in the crx-quickstart folder to retrieve the exact product version numberAffected if The installed version is below 6.5.20.0 or below 2024.3.0 (for AEM as a Cloud Service)
-
Determine if AEM Forms module is in useCheck the AEM package manager or examine the /libs/fd/fm content structure to see if Forms add-on or Adaptive Forms functionality is installed and enabledAffected if AEM Forms is installed and form-based content creation is permitted for authenticated users
-
Review form field configurationsNavigate to the Forms/Adaptive Forms configuration in AEM Assets or the form authoring UI and inspect form field components to see if input validation or output encoding settings are present or disabledAffected if Form fields allow unrestricted text input without proper encoding or content validation policies applied
-
Inspect form submission content for suspicious payloadsQuery the repository under /content/forms or /content/dam/forms for stored form submissions and examine field values for JavaScript tags, script elements, or event handler attributes (onload, onerror, onclick, etc.)Affected if Stored form submission data contains unsanitized HTML, script tags, or JavaScript event handlers in form field values
You are affected if your AEM version is below 6.5.20.0 or below 2024.3.0 AND authenticated users can create or edit form fields that accept user input, as the vulnerability allows stored XSS injection into those form fields.
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
Upgrade Adobe Experience Manager to version 6.5.20 or later to patch the vulnerability. Review and sanitize existing user-generated content in form fields for any existing malicious scripts.
6.5.20.0 (on-premise 6.5.x line); 2024.3.0 or later (AEM cloud)
- Verify current Adobe Experience Manager version by checking the product console or system information
- Plan upgrade during a maintenance window with proper backup of AEM instance and content repository
- For on-premise AEM 6.5.x installations: Upgrade to version 6.5.20.0 or later
- For AEM cloud instances: Upgrade to version 2024.3.0 or later
- After upgrade, verify the stored XSS vulnerability is resolved by testing form field input validation
- Clear any cached content to ensure the patched version is fully deployed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26096 — 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-26096 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