CVE-2026-27247
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. A low-privileged attacker can inject malicious JavaScript that persists in the system and executes when victims 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 your AEM versionNavigate to the AEM Welcome page or check the com.adobe.granite.package version via the Felix console at /system/console/bundles. Look for the Core CMS version in the About Adobe Experience Manager section.Affected if The installed version is 6.5.23 or earlier, or falls below 6.5.24.0, or is version 6.5.x before the 2026.2.0 update.
-
Identify active form implementationsReview your AEM instance for any deployed adaptive forms, core form components, or custom form field components. Check the /content/forms/af directory and related form models in the CRX/DE repository.Affected if The instance uses form fields for user input, as the vulnerability exists specifically in form field processing.
-
Inspect form field configurations for unsanitized inputExamine the XML or JSON configurations of form field components in CRX/DE Lite at /apps or /conf. Look at the properties of Adaptive Form Field, Text Field, and similar components for any unvalidated input patterns.Affected if Form field components allow raw HTML or script tags in their validation patterns, placeholders, or label properties without server-side encoding.
-
Search for persisted script payloadsQuery the repository using CRXDE or the Query Builder at /libs/cq/search/content/queryconsole for form field nodes containing script tags (script, javascript:, onerror, onload) in text properties.Affected if Any form field data in the repository contains persisted JavaScript code or HTML script tags that could execute when the form is rendered.
You are affected if your AEM version is 6.5.23 or earlier (below 6.5.24.0) or below 2026.2.0, AND you have form fields that accept and persist unsanitized user input where malicious scripts could execute.
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
Update AEM to version 6.5.24 or later to patch the vulnerability, and implement proper input validation and output encoding for all form fields.
6.5.24.0 or later; or 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 that release track is preferred
- After upgrading, verify that the XSS vulnerability is resolved by testing 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.
- 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-27247 — 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-27247 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