CVE-2026-27240
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-privilege authenticated attacker can inject malicious JavaScript payloads into vulnerable form input fields, which are then stored and executed in the browsers of users who view the 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.
-
Identify AEM versionAccess the AEM About page at /libs/granite/ui/content/shell/about.html or check the productinfo.xml in the installation directory. Alternatively, query the JMX console or bundle information via the OSGi Web Console at /system/console/bundlesAffected if The installed version is < 6.5.24.0, < 2026.2.0, or equals 6.5.x
-
Verify AEM Forms module is enabledCheck if the AEM Forms addon is installed by navigating to /libs/fd/fm/view or by reviewing installed packages in the Package Manager at /crx/packmgr/list.jspAffected if AEM Forms is installed and accessible to low-privilege users
-
Identify exposed form endpointsReview the Forms UI at /aem/forms/ or check the HTML source of published form pages for input fields that accept user-supplied data. Look for form containers under /content/forms/afAffected if Form fields that accept user input are publicly or low-privilege accessible
-
Check for unencoded form field outputInspect the HTML response of saved form submissions or preview pages. Look for user input rendered directly in the page without HTML encoding (for example, raw <script> tags appearing in the DOM)Affected if User input in form fields is displayed without proper output encoding, allowing script execution
You are affected if AEM version is less than 6.5.24.0 or less than 2026.2.0 AND low-privilege users can access form fields where injected JavaScript can be stored and rendered to other users.
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 Adobe Experience Manager to version 6.5.24 or later, which contains the security patch for this stored XSS vulnerability. Alternatively, implement output encoding and input validation on affected form fields as a compensating control.
6.5.24.0 (for 6.5.x line) or 2026.2.0+ (for newer release track)
- Identify the current Adobe Experience Manager version by checking the product dashboard or system information
- Review current AEM instance for custom code, third-party integrations, and dependencies that may be affected by an upgrade
- Schedule maintenance window for the upgrade process
- Back up the current AEM instance including repository, database, and configurations
- Upgrade Adobe Experience Manager to version 6.5.24.0 or later (or 2026.2.0+ for the newer release track)
- Verify the upgrade completed successfully by checking the version number
- Test the form fields that were previously vulnerable to confirm the XSS vulnerability is remediated
- Deploy to production after successful testing in non-production environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27240 — 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-27240 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