dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-47972

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 6.5.25.0 / 2026.5.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.24, LTS SP1, 2026.04 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. Scope is changed.

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager allows low-privileged attackers to inject malicious JavaScript into form fields. The malicious payload is stored and executes in victims' browsers when they view affected pages. The CVSS scope changed, indicating the vulnerability can impact resources beyond the vulnerable component.

MitigationApply the vendor patch by updating to Adobe Experience Manager version 6.5.25, LTS SP2, or 2026.05 or later. Implement Content Security Policy (CSP) headers as defense-in-depth.

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.25.0< 2026.5.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. Identify Adobe Experience Manager version
    Access the AEM Welcome page (/aem/start.html) or go to Help > About Adobe Experience Manager. Alternatively, check the version.properties file in the crx-quickstart folder or inspect the system console at /system/console/bundles to locate the AEM core bundle version.
    Affected if The installed version is any 6.5.x version below 6.5.25.0, or any version below 2026.5.0 (including older 6.x releases).
  2. Confirm Forms or Adaptive Forms are in use
    Navigate to the AEM Forms interface at /aem/forms or check for form-related content fragments or adaptive form components in the Assets console under /content/forms/af.
    Affected if Adobe Experience Manager Forms module is enabled and form fields are present in the environment.
  3. Check for user-created form content
    Search the CRX/DE repository (accessible at /crx/de) under /content/forms for submitted form data or form definitions. Look in the datastore for any form-related nodes.
    Affected if Form submissions or form field definitions exist in the repository, providing an attack surface for XSS injection.
  4. Identify low-privileged user accounts
    Review user and group permissions in the User Management console at /libs/granite/security/content/useradmin or check the groups under /home/groups for accounts with limited (contributor/author) permissions.
    Affected if Low-privileged user accounts exist in the system who could potentially inject malicious scripts into form fields.

You are affected if your AEM version is below 6.5.25.0 or below 2026.5.0 AND you have Adobe Experience Manager Forms enabled with form fields that accept user input.

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.25.0 / 2026.5.0 or later
Fixed in 6.5.25.02026.5.0
Interim mitigation

Apply the vendor patch by updating to Adobe Experience Manager version 6.5.25, LTS SP2, or 2026.05 or later. Implement Content Security Policy (CSP) headers as defense-in-depth.

Recommended fix High confidence

Adobe Experience Manager 6.5.25.0 (LTS track) or 2026.5.0 (2026 release track)

  1. Backup the Adobe Experience Manager instance before proceeding with any upgrade
  2. Review the Adobe Experience Manager 6.5.25.0 (for 6.5 LTS) or 2026.5.0 (for 2026 release) release notes for any additional changes or prerequisites
  3. Upgrade Adobe Experience Manager to version 6.5.25.0 if using the 6.5 LTS track, or to version 2026.5.0 if using the 2026 release track
  4. Test the upgrade in a non-production environment before deploying to production
  5. Verify the stored XSS vulnerability is remediated by testing the previously vulnerable form fields

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47972 — 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-47972 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