CVE-2026-27251
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 vulnerability in form fields that allows low-privileged attackers to inject malicious JavaScript. When victims browse to pages containing the compromised form fields, the embedded script executes in their browsers, potentially allowing session hijacking or data theft.
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< 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.
-
Confirm Adobe Experience Manager is installedCheck for AEM processes running on common ports (4502, 4503) or look for AEM installation directories containing 'crx-quickstart' or 'aem' in the file systemAffected if AEM is not present in the environment, this CVE does not apply
-
Identify installed AEM versionAccess the AEM welcome page at /libs/granite/core/content/login.html or check the version.properties file in the crx-quickstart folder, or run: java -jar cq-author-*.jar -versionAffected if The version is 6.5.23 or earlier, or exactly 6.5, or any version less than 2026.2.0 - this indicates the environment contains the vulnerable code
-
Check for form field usage in AEMReview AEM forms created using Core Components (form container, text input, number input components) or Foundation form components under /libs/foundation/components/form/Affected if AEM forms with user-submitted fields are present and accessible to low-privileged users, creating the attack surface for XSS injection
-
Inspect form field data for suspicious contentQuery the AEM repository (CRXDE Lite at /crx/de) or use the Query Builder to search for form submission data in /content or look for any script tags in form-related nodesAffected if Malicious JavaScript code (script tags, event handlers like onerror, onload) is found stored in form field content nodes
The environment is affected if AEM version is 6.5.23 or earlier (or < 2026.2.0) AND forms with user-submittable fields are in use, allowing stored XSS injection to execute in victim browsers.
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.242026.2.0
Upgrade Adobe Experience Manager to a version newer than 6.5.23, or implement proper input validation and output encoding on affected form fields to prevent script injection.
AEM 6.5.24 or later
- Upgrade Adobe Experience Manager to version 6.5.24 or later to resolve the stored XSS vulnerability
- Verify the upgrade in a non-production environment before deploying to production
- After upgrading, test that the vulnerable form fields no longer accept malicious script injections
- Ensure all custom code and third-party integrations are compatible with the new version
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-27251 — 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-27251 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