CVE-2026-27228
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 into vulnerable form inputs, which persists in the system and executes when other users view the affected page in their browser.
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 installed AEM versionNavigate to AEM Welcome page > Tools > Operations > Diagnosis, or access /system/console/configMgr and look for com.day.cq.commons.impl.VersionInfoImpl to retrieve the current AEM version numberAffected if The installed version is below 6.5.24.0 or below 2026.2.0 (e.g., 6.5.0 through 6.5.23 are all affected)
-
Confirm Forms or Adaptive Forms feature is enabledCheck if the Forms add-on package is installed: navigate to /crx/packmgr and look for 'aem-forms' packages, or access /libs/forms to confirm the Forms framework is presentAffected if Forms or Adaptive Forms modules are installed and accessible in the AEM instance
-
Verify low-privileged user access to form creation or editingLog in as a user with minimal permissions (such as a standard 'user' or 'content-author' group member) and attempt to access Forms functionality at /aem/forms or create an Adaptive Form; check user group memberships in /useradminAffected if Low-privileged authenticated users can access, create, or edit form fields in AEM Forms
-
Inspect existing form data for suspicious contentQuery the repository at /content/forms/af or /content/dam/formsanddocuments for stored form submissions; use CRXDE Lite (/crx/de) to examine form field nodes in the JCR for any unexpected script tags or event handlersAffected if Form field data contains unencoded HTML, script tags, or JavaScript event handlers (e.g., <script>, onclick, onerror)
You are affected if your AEM version is below 6.5.24.0 or below 2026.2.0 AND Forms/Adaptive Forms are enabled with accessible form fields that low-privileged users can populate.
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 to AEM 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 / 2026.2.0 or later
- Upgrade Adobe Experience Manager to version 6.5.24.0 or later
- Alternatively, upgrade to version 2026.2.0 or later if using the newer release naming
- After upgrade, verify the XSS vulnerability is resolved by testing form field inputs
- Review Adobe's release notes for the target version for any additional security patches
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27228 — 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-27228 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