dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-47970

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

Adobe Experience Manager versions 6.5.24 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. Low-privileged attackers can inject malicious JavaScript that executes in victim browsers when they view pages containing the compromised fields. The scope change indicates the vulnerability impacts components beyond the initially vulnerable form.

MitigationApply the vendor patch for CVE-2026-47970 and implement output encoding/HTML sanitization on all form fields handling user input. Consider Content Security Policy 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 AEM installation
    Check for Adobe Experience Manager by looking for the 'aem' process running, or locate AEM installation directories (common paths: /opt/aem, /Program Files/Adobe, /mnt/aem). Check for AEM-specific files like 'cq-quickstart' or 'author' folders.
    Affected if AEM is not found on the system (not applicable)
  2. Determine installed AEM version
    Locate the version file in the AEM installation directory, typically at [aem-install]/crx-quickstart/conf/org.apache.felix.framework.info.properties or access AEM System Information via the console at /system/console/systeminfo. The version is also visible on the Welcome page.
    Affected if Unable to determine version (may not be AEM)
  3. Compare version against affected ranges
    Check if the installed version is: any 6.5.x version below 6.5.25.0, any version below 2026.5.0, or exactly 6.5 without service packs. If version shows 6.5.0 to 6.5.24.x, or 2026.0 to 2026.4.x, or simply '6.5' without additional numbers, the version is affected.
    Affected if Installed version is < 6.5.25.0 OR < 2026.5.0 OR equals exactly 6.5 (base release without service pack)
  4. Verify presence of form authoring capability
    Confirm AEM Forms or Adaptive Forms module is enabled by checking /system/console/bundles for 'aem-forms' bundles or checking if /libs/fd/af paths exist in the AEM repository. The XSS affects form fields, so form functionality must be present.
    Affected if Forms or Adaptive Forms modules are installed and enabled

The environment is affected if Adobe Experience Manager is installed with a version matching < 6.5.25.0, < 2026.5.0, or exactly 6.5, and the Forms module is present.

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 for CVE-2026-47970 and implement output encoding/HTML sanitization on all form fields handling user input. Consider Content Security Policy headers as defense-in-depth.

Recommended fix High confidence

AEM 6.5.25.0 or later for 6.5.x LTS; AEM 2026.5.0 or later for as-a-cloud-service

  1. Identify your current Adobe Experience Manager version by checking the system console or version.properties file
  2. Backup your AEM instance and all content repositories before proceeding
  3. For AEM 6.5.x (LTS) deployments: Upgrade to version 6.5.25.0 or later
  4. For AEM as a Cloud Service deployments: Upgrade to version 2026.5.0 or later
  5. After upgrading, clear the AEM cache and rebuild any search indexes if applicable
  6. Verify the upgrade was successful by confirming the new version number in the system console
  7. Test that the vulnerable form fields no longer execute stored XSS payloads
Caveat Review Adobe's release notes for the target version for potential breaking changes; custom components or integrations may require testing

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
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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