CVE-2026-27233
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 authenticated attacker can inject malicious JavaScript payloads into vulnerable form input fields, which are then stored and rendered when other users view the affected pages, enabling session hijacking 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.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 AEM installation versionAccess the AEM Welcome page or check the product version through the system console (typically /system/console/bundles or /crx/packmgr/service.jsp). Locate the exact version number displayed in the AEM About page (Help > About Adobe Experience Manager).Affected if The installed version is earlier than 6.5.24.0, earlier than 2026.2.0, or falls within the 6.5.x line before the patched releases.
-
Confirm authenticated access is possibleVerify whether user accounts with low-privileged permissions (such as standard author or contributor roles) can log into the AEM instance. Attempt to access the Forms section or Content Fragments area with a test low-privilege account.Affected if Low-privileged authenticated users have access to create or edit form content within AEM.
-
Locate form field configurationsNavigate to the AEM Forms or Adaptive Forms interface (typically /aem/forms or through the Forms tile in AEM Assets). Identify whether any form field definitions exist in the content repository under /content/forms or similar paths.Affected if Form fields are present and accessible for editing by authenticated users in the environment.
-
Inspect stored form data for unsanitized contentUsing CRX/DE (accessible at /crx/de), search the content repository for form-related nodes under /content/forms or /etc/cloudservices. Examine stored field values for any HTML or script tags that may have been injected into text input fields.Affected if Form field nodes contain raw unencoded HTML or script tags in their values, indicating the XSS vulnerability is present and exploitable.
-
Review form field output renderingAccess published or preview instances of pages containing form fields. Use browser developer tools to inspect the HTML source of rendered form inputs. Look for the presence of unescaped characters in attribute values or content displayed from form submissions.Affected if Form field outputs render user-supplied content without proper HTML encoding or sanitization on the rendered pages.
You are affected if your AEM version is earlier than 6.5.24.0 or 2026.2.0, low-privileged authenticated users can access form fields, and those form fields render stored content 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
Apply the vendor patch for AEM 6.5.23 or later; until then, implement output encoding for all form field outputs and consider restricting low-privileged user permissions to form creation/editing.
AEM 6.5.24.0 or later (or AEM 2026.2.0+ if using that release line)
- 1. Back up your current Adobe Experience Manager instance and content repository
- 2. Review Adobe Experience Manager 6.5.24.0 release notes for any breaking changes relevant to your implementation
- 3. Test the upgrade in a non-production environment first
- 4. Upgrade Adobe Experience Manager from version 6.5.23 or earlier to version 6.5.24.0 or later
- 5. Alternatively, if using the 2026.x release line, upgrade to version 2026.2.0 or later
- 6. Verify the upgrade was successful and all custom code/functions still work as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27233 — 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-27233 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