CVE-2026-27231
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.23 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.23 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability where malicious scripts can be injected into form fields and executed in victims' browsers when they view the affected page.
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.24.0< 2026.2.0= 6.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.
-
Check AEM product versionAccess the AEM System Information console at /system/console/status-productinfo or check the crx-quickstart/package.xml file for the installed version numberAffected if Installed version is 6.5.x where x <= 23, or version is earlier than 6.5.24.0, or version is earlier than 2026.2.0 (for cloud/ongoing releases)
-
Identify form components in useReview AEM form components deployed in your content pages. Check the page source or use the AEM Template Editor to list form field components (specifically those handling user input that may be stored)Affected if Form components that accept and store user input are present on published pages without proper output encoding
-
Inspect stored form data for malicious scriptsQuery the AEM content repository (via CRXDE Lite at /crx/de or using the Query Builder API) for form submission nodes that contain script tags, javascript: URLs, or event handler attributes in field valuesAffected if Repository contains form entries with unsanitized script tags or event handlers in input fields
-
Review form field output encodingExamine the HTL/Sightly templates or JSPs that render form field values on the affected pages. Look for use of context-aware escaping functions vs. raw output of form dataAffected if Form values are rendered using raw output (e.g., without xss:attr, xss:attr, or context-specific escaping)
A user is affected if their installed AEM version is less than 6.5.24.0 (or less than 2026.2.0 for ongoing releases) AND they have form components that store user input rendered 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.24.02026.2.0
Apply the Adobe security patch for AEM or implement output encoding/sanitization on the vulnerable form fields to prevent script injection.
AEM 6.5.24.0 or later / AEM 2026.2.0 or later
- 1. Back up the current AEM instance including the repository, configurations, and any custom code
- 2. Review the Adobe Experience Manager upgrade documentation for your current version
- 3. Test the upgrade in a non-production environment first to verify compatibility
- 4. Apply the upgrade to AEM 6.5.24.0 or later (or 2026.2.0 or later for the 2026.x branch)
- 5. Verify the XSS vulnerability is remediated by testing the previously vulnerable form fields
- 6. Conduct full functional testing of the application post-upgrade
- 7. Deploy the validated upgrade to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27231 — 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-2026-27231 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