dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-47942

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 · moderate confidence

Adobe Experience Manager versions 6.5.24, LTS SP1, 2026.04 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privileged authenticated attacker can inject malicious JavaScript that persists in the system and executes when other users view pages containing the affected fields.

MitigationUpdate to a patched Adobe Experience Manager version beyond 6.5.24/LTS SP1/2026.04, and implement proper input validation and output encoding for all form 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
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 installation
    Locate AEM by checking for the typical installation directory (commonly at /opt/aem, /crx, or C:\Program Files\Adobe) or by accessing the AEM login page (usually at /libs/granite/core/content/login.html or the author/publish instance URLs).
    Affected if AEM is present and accessible in the environment.
  2. Determine installed AEM version
    Access the AEM Web Console (System > Information) at /system/console/configMgr or check the crx-quickstart/package.version file in the AEM installation directory. Alternatively, append ?v to the login page URL to view version information.
    Affected if The displayed version falls within < 6.5.25.0, < 2026.5.0, or equals exactly 6.5.
  3. Verify low-privilege user access to form inputs
    Log in with a low-privilege user account (such as a standard user or contributor) and navigate to pages containing custom form components or user-generated content fields. Determine if these forms accept and save user input.
    Affected if Low-privilege users can submit or edit content in form fields.
  4. Identify custom or third-party form components
    Review the AEM component list under Tools > Assets > Content Fragment Models or check /apps for custom form components that handle user input. Inspect whether these components implement output encoding on displayed values.
    Affected if Custom form components are in use that do not perform output encoding on saved data.

A user is affected if they run any AEM version matching < 6.5.25.0, < 2026.5.0, or = 6.5 AND have custom form fields accessible to low-privilege users without proper output encoding.

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

Update to a patched Adobe Experience Manager version beyond 6.5.24/LTS SP1/2026.04, and implement proper input validation and output encoding for all form fields.

Recommended fix High confidence

AEM 6.5.25.0 or AEM 2026.5.0 (and later)

  1. 1. Identify current Adobe Experience Manager version by checking the AEM welcome page or using the version manifest in the crx-quickstart folder
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Perform a complete backup of the AEM instance including repository, database, and configuration files
  4. 4. Review and resolve any pre-upgrade compatibility issues documented in the Adobe Experience Manager documentation
  5. 5. Download Adobe Experience Manager version 6.5.25.0 or later (or 2026.5.0+ for the newer release line) from the Adobe Software Distribution portal
  6. 6. Follow Adobe's official upgrade instructions to apply the new version
  7. 7. After upgrade, verify that all custom applications and workflows function correctly
  8. 8. Test the specific form fields that were previously vulnerable to confirm the XSS fix is effective
Caveat Review Adobe's release notes for version 6.5.25.0 for any deprecated features or configuration changes that may require adjustments in custom code or integrations

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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