CVE-2024-26087
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 in form fields. Attackers can inject malicious JavaScript into vulnerable form inputs, which persists in the system. When users view pages containing these compromised fields, the malicious script executes in their browsers, enabling session hijacking, credential theft, or defacement.
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 the installed Adobe Experience Manager versionAccess the AEM Welcome page or check the version file in the installation directory. On the AEM landing page, look for the version number displayed, or query the system via the Version Info endpoint (e.g., /system/console/bundles or check the crx-quickstart/versions.properties file).Affected if The installed version is lower than 6.5.20.0 or lower than 2024.3.0
-
Identify if AEM Forms or Adaptive Forms modules are enabledNavigate to the AEM Forms console (typically at /aem/forms) or check the list of installed packages via the Package Manager to confirm whether the Forms add-on is installed and active.Affected if Forms functionality is installed and active, as the vulnerability exists in form fields
-
Audit custom form components or form containersReview the /apps directory for custom form field components (look under /apps for components with 'form' or 'field' in the path). Inspect the JSP, HTML, or HTL templates for these custom components to see if they implement input validation or output encoding.Affected if Custom form components exist that do not implement proper output encoding on user input
-
Check form field input validation configurationExamine Adaptive Form models or form field configurations in the repository (under /content/forms/af) to verify whether input validation rules are applied to form fields, and whether they allow unrestricted text input.Affected if Form fields lack input validation constraints or allow script tags in their accepted values
-
Review content rendering for stored form dataCreate a test form field, inject a benign script tag (e.g., <script>alert('test')</script>) into a text field, save the form, and then view the submitted data or a page that renders that submitted value to see if the script executes.Affected if The submitted form value is rendered without encoding and the script executes in the browser
You are affected if your AEM version is below 6.5.20.0 or below 2024.3.0, and you have Forms or Adaptive Forms enabled with fields that accept user input rendered without 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.20.02024.3.0
Upgrade Adobe Experience Manager to version 6.5.20 or later to obtain the patched version. Additionally, implement input validation and output encoding on form fields, and configure Content-Security-Policy headers to mitigate XSS execution.
6.5.20.0 or 2024.3.0
- 1. Back up your current Adobe Experience Manager instance and database
- 2. Review the Adobe Experience Manager 6.5.20.0 or 2024.3.0 release notes for any migration requirements
- 3. Upgrade your Adobe Experience Manager instance to version 6.5.20.0 or later, or to version 2024.3.0 or later
- 4. After upgrading, verify that the stored XSS vulnerability is remediated by testing the affected form fields
- 5. Ensure your upgraded instance is functioning correctly before deploying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26087 — 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-26087 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