CVE-2026-27249
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 versions 6.5.23 and earlier allows low-privileged authenticated users to inject malicious JavaScript into form fields. The malicious payload persists in the system and executes in victim users' browsers when they view pages containing the compromised fields.
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.
-
Check installed AEM versionNavigate to the AEM Welcome page or access the system information via the Help menu, or query the version endpoint at /system/console/bundles or check the crx-quickstart/package-version.info file. Compare the displayed version against the affected ranges: versions < 6.5.24, < 2026.2.0, or 6.5.x where x <= 23.Affected if The installed version is 6.5.23 or earlier, or falls within the 6.5.x line before 6.5.24, or is below 2026.2.0.
-
Verify if AEM Forms or Adaptive Forms module is enabledAccess the AEM Forms interface by navigating to /aem/forms or checking the Felix Console at /system/console/bundles for 'adobe-aemforms-*' bundles. Look for installed and active Forms-related bundles.Affected if Forms or Adaptive Forms bundles are installed and active, providing the input fields where the XSS payload could be injected.
-
Identify custom form components without input validationReview the /apps directory in CRXDE Lite (accessible at /crx/de) for custom form components under /apps/myproject/components or similar custom component paths. Check the JSP, HTL, or Java files for presence of output encoding functions like XSS API, ESAPI encoder, or standard encoding methods.Affected if Custom form components exist that accept user input but lack proper server-side output encoding, creating the condition for stored XSS.
-
Inspect form field configurations for missing output encodingExamine form field definitions in the repository at /conf or /content, looking at the model or XML definitions for Adaptive Forms or Foundation Form components. Verify if the 'translations' or 'display format' properties contain raw user-supplied values.Affected if Form field configurations allow raw HTML or JavaScript to be stored and rendered without encoding when the form is displayed to other users.
Your environment is affected if AEM version is below 6.5.24 or below 2026.2.0 AND Forms/Adaptive Forms are enabled with form fields that accept user input without server-side 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.242026.2.0
Update Adobe Experience Manager to version 6.5.24 or later to obtain the vendor patch. Implement Content Security Policy (CSP) headers and enforce input validation/output encoding on form fields as defense-in-depth measures.
6.5.24 (6.5.x line) or 2026.2.0 (2026.x line)
- Backup your current Adobe Experience Manager instance and database
- Review the Adobe Experience Manager 6.5.24 release notes for any known issues or breaking changes
- Test the upgrade in a non-production environment first
- Upgrade Adobe Experience Manager to version 6.5.24 or later (for 6.5.x line)
- Alternatively, upgrade to version 2026.2.0 or later (for the 2026.x line)
- Verify the upgrade was successful and all services are running
- Test the specific form fields that were vulnerable to ensure the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27249 — 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-27249 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