CVE-2026-27236
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 a low-privileged 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 low-privileged users can inject malicious JavaScript into vulnerable form fields. The injected script persists on the affected page and executes in victim users' browsers when they view the compromised content.
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.
-
Identify the installed AEM versionAccess the AEM System Information console at /system/console/status-productinfo or check the version.properties file in the crx-quickstart directory. Alternatively, navigate to Help > About Adobe Experience Manager in the classic UI.Affected if The version is 6.5.23 or earlier, any 6.5.x version below 6.5.24.0, or any version below 2026.2.0
-
Verify if low-privileged user access to form components existsReview the user permissions in AEM Groups and Permissions (Tools > Security > Permissions). Check if users with limited privileges (such as content authors or contributors) have write access to form field components in Content Fragments, Experience Fragments, or Adaptive Forms.Affected if Low-privileged users can create or edit content containing form input fields without administrative oversight
-
Confirm presence of unvalidated form input fieldsInspect form components in your AEM instance (Adaptive Forms, Core Components with form fields, or custom form containers). Check the input validation configuration in the component's edit dialog under the Validation tab or in the Granite DataTypes schema.Affected if Form fields do not have strict input validation enabled (required=true, type=string with pattern constraints) or allow raw HTML/script input
-
Check if output encoding is applied to form field outputsExamine the HTL/Sightly templates rendering the form fields. Look for context-aware output encoding such as ${properties.fieldName @ context='html'} or ${properties.fieldName @ context='attribute'}. Inspect the Source Edit mode in Rich Text Editor if used.Affected if Form field values are rendered without proper context-aware encoding, allowing stored scripts to execute in victim browsers
You are affected if your AEM version is 6.5.23 or earlier, below 6.5.24.0, or below 2026.2.0 AND low-privileged users can inject content into form fields that are 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.24.02026.2.0
Upgrade Adobe Experience Manager to a version newer than 6.5.23. Implement strict input validation and output encoding on all form fields, and consider adding Content-Security-Policy headers to mitigate XSS risks.
6.5.24.0 (or 2026.2.0+ for the cloud/other variant)
- 1. Create a complete backup of the current Adobe Experience Manager instance including content repository and configurations
- 2. Review Adobe's upgrade documentation for version 6.5.24.0 (or 2026.2.0 for cloud/other variant) before proceeding
- 3. Perform the upgrade to Adobe Experience Manager version 6.5.24.0 or later (or 2026.2.0+)
- 4. After upgrade, verify the AEM instance is running correctly and all services are operational
- 5. Test the previously vulnerable form fields to confirm the XSS vulnerability has been remediated
- 6. Clear any caches and rebuild search indexes if necessary post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27236 — 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-27236 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