CVE-2026-27266
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 in form fields. A low-privileged attacker can inject malicious JavaScript into vulnerable form inputs, which persists in the system and executes when other users browse to affected pages.
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 installed AEM versionNavigate to the AEM Welcome page or access the system information via the Help menu. The version number is displayed on the AEM Welcome screen.Affected if Version is 6.5.23 or earlier, any 6.5.x version below 6.5.24.0, or any version below 2026.2.0
-
Identify form components in useReview the /apps and /content directories in CRX/DE for form-related components. Look for adaptive forms, core WCM components using form elements, or custom form implementations.Affected if The instance uses form components that accept and store user input without server-side input validation
-
Verify low-privileged user permissions for formsCheck user group permissions in AEM User Management. Determine if users with content-author or lower privileges can create, edit, or submit form content.Affected if Low-privileged users have write access to form components or form submission content
-
Inspect stored form data for unsanitized inputUse CRX/DE or query the repository for form submission nodes in /content, /var, or application-specific paths. Examine stored values for raw HTML, script tags, or JavaScript event handlers.Affected if Form submission data contains unescaped HTML or JavaScript such as script tags, javascript: URLs, or event attributes like onerror or onload
If the AEM version falls within the affected range and the instance hosts form components accessible to low-privileged users, the environment is likely vulnerable to stored XSS via this CVE.
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 AEM to a patched version (6.5.24 or later). Additionally, implement input validation and output encoding on form fields, and configure Content-Security-Policy headers to mitigate XSS execution.
Adobe Experience Manager 6.5.24.0 or later
- 1. Backup your current Adobe Experience Manager instance and database
- 2. Review Adobe's upgrade documentation for 6.5.24.0 at helpx.adobe.com
- 3. Download Adobe Experience Manager 6.5.24.0 (or latest 6.5.x release) from the Adobe distribution portal
- 4. Test the upgrade in a non-production environment first
- 5. Deploy the upgrade to production following standard AEM maintenance procedures
- 6. Verify the XSS vulnerability is remediated by testing the form fields that were previously vulnerable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27266 — 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-27266 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