CVE-2026-27265
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager 6.5.23 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. The malicious payload persists on the page and executes in victims' browsers when they view the affected 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.
-
Determine AEM product versionNavigate to the AEM Welcome page or check the version file in the crx-quickstart folder, or query the version endpoint at /system/console/branding. Compare the displayed version number against the affected ranges: < 6.5.24.0, < 2026.2.0, or any 6.5.x release.Affected if The installed version is 6.5.23.0 or earlier, or any 6.5.x release, or any version below 2026.2.0.
-
Verify Forms feature is enabledCheck if AEM Forms or Core Components with form capabilities are installed and accessible. Navigate to /libs/granite/corecomponents/form or verify Forms bundles are active in /system/console/bundles.Affected if Forms functionality is present and accessible to low-privileged users.
-
Inspect stored form content for malicious payloadsQuery the JCR repository using CRXDE Lite or a Groovy script to search form field nodes under /content for suspicious patterns like <script>, javascript:, onerror=, or other XSS vectors in field values.Affected if Form field nodes contain unsanitized HTML or script tags that could execute in a victim's browser.
-
Review form field input validation settingsCheck the Granite DataTypes or form field component dialog configurations under /apps or /libs for the presence of input validation rules. Inspect the HTL/Sightly templates rendering form fields for output encoding implementation.Affected if Form fields lack server-side input validation or proper output encoding is not applied in the rendering layer.
You are affected if your AEM version is below 6.5.24.0 (or below 2026.2.0), Forms are enabled, and form fields are accessible to low-privileged users without proper input validation and 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
Implement strict input validation and output encoding on all form fields in AEM; consider upgrading to a patched AEM version if available and implementing Content Security Policy headers to mitigate XSS risks.
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 train
- After upgrading, verify that the XSS vulnerability is remediated by testing the form fields that were previously vulnerable
- Ensure proper testing in a non-production environment before deploying the upgrade to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27265 — 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-27265 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