dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-27252

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 6.5.24 / 2026.2.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Adobe 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 confidence

A stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.23 and earlier allows low-privileged users to inject malicious JavaScript into form fields. The injected script persists in the system and executes in victim browsers when they navigate to pages containing the compromised fields.

MitigationApply Adobe's security patch for this vulnerability (upgrade to AEM 6.5.24 or later). Until then, implement strict input validation and output encoding on all form fields, and consider restricting low-privilege user permissions to form creation/editing.

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
Experience ManagerApplication
Affected:< 6.5.24< 2026.2.0= 6.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check your AEM version
    Navigate to the AEM Welcome page or check the com.adobe.version file in the crx-quickstart folder. You can also query the system console at /system/console/status-productinfo to retrieve the exact installed version.
    Affected if The installed version is 6.5.23 or earlier, 6.5 (any patch level), or any version below 2026.2.0.
  2. Identify form components in use
    Review your AEM instance for form components under /libs/foundation/components/form or custom form implementations. Check the content structure under /content for pages containing form fields.
    Affected if Form components that accept user input are present and accessible on the instance.
  3. Audit low-privilege user permissions
    Open the User Administration console at /useradmin. Review user groups assigned 'content-author' or similar low-privilege roles. Verify which users can create or edit form content under /content.
    Affected if Low-privilege users (non-admin) have permission to create, edit, or modify form field content.
  4. Inspect form field data for malicious content
    Use CRXDE Lite (accessible at /crx/de) or the Query tool to search form content nodes under /content. Look for stored scripts in form field values (check for <script> tags, javascript: URIs, or event handlers like onload, onerror).
    Affected if Any form field values contain unsanitized script tags or JavaScript event handlers.

Your environment is affected if you run AEM version 6.5.23 or earlier (or < 2026.2.0), have form components in use, allow low-privilege users to edit form fields, and especially if malicious script content is already present in form data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.5.24 / 2026.2.0 or later
Fixed in 6.5.242026.2.0
Interim mitigation

Apply Adobe's security patch for this vulnerability (upgrade to AEM 6.5.24 or later). Until then, implement strict input validation and output encoding on all form fields, and consider restricting low-privilege user permissions to form creation/editing.

Recommended fix High confidence

Adobe Experience Manager 6.5.24 or later / 2026.2.0+

  1. 1. Identify the current Adobe Experience Manager version by checking the system console or AEM version file
  2. 2. Plan the upgrade during a maintenance window following Adobe's upgrade documentation
  3. 3. Back up the current AEM instance including repository, database, and configurations
  4. 4. Upgrade Adobe Experience Manager to version 6.5.24 or later (or to 2026.2.0+ if using the newer release cadence)
  5. 5. Verify the upgrade was successful by checking the AEM version in the system console
  6. 6. Test the fix by attempting to inject script tags into vulnerable form fields to confirm XSS is no longer possible
  7. 7. Clear AEM caches and publish any content changes if necessary
Caveat Review Adobe's 6.5.24 release notes for any compatibility changes; major version upgrades may require testing of custom code and configurations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27252 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27252 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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