dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-47950

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager forms allowing low-privileged authenticated users to inject malicious JavaScript that executes in victim browsers when viewing pages with affected form fields. The scope change indicates the vulnerability can impact resources outside the vulnerable component.

MitigationImplement strict input validation and output encoding for all form fields in AEM, apply Content Security Policy headers to mitigate XSS execution, and review form components for proper sanitization of user-supplied content.

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 installed AEM version
    Navigate to the AEM Welcome page and check the version information, or query the system console (/system/console/systeminfo) for the Adobe Experience Manager product version.
    Affected if The installed version is 6.5.24, LTS SP1, 2026.04, or any version < 6.5.25.0, < 2026.5.0, or equal to 6.5.
  2. Confirm Forms or Adaptive Forms feature is enabled
    Check if the AEM Forms addon is installed by navigating to Tools > Forms or reviewing the package manager for forms-related packages.
    Affected if AEM Forms or Adaptive Forms functionality is present in the environment.
  3. Review form field creation permissions for low-privileged users
    Navigate to Tools > Security > Permissions or the User Administration console, and examine the permissions assigned to non-admin user groups, specifically checking for write access to form content or adaptive form models.
    Affected if Low-privileged authenticated users (non-admin) have permissions to create or edit form fields.
  4. Inspect form field configurations for unsanitized output
    Review the form field component XML configurations (located in /apps or /conf) for any custom form components that may lack proper input validation or output encoding settings.
    Affected if Custom form field components exist that do not implement input validation or output encoding.

The environment is affected if the installed AEM version falls within the vulnerable range (6.5.24, LTS SP1, 2026.04 or earlier) AND the Forms feature is enabled with low-privileged users having form field editing permissions.

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

Implement strict input validation and output encoding for all form fields in AEM, apply Content Security Policy headers to mitigate XSS execution, and review form components for proper sanitization of user-supplied content.

Recommended fix High confidence

6.5.25.0 or later (LTS); 2026.5.0 or later (newer release)

  1. 1. Back up the current Adobe Experience Manager instance including repository, configuration, and custom code.
  2. 2. Test the upgrade in a non-production environment first.
  3. 3. Upgrade Adobe Experience Manager to version 6.5.25.0 or later for the 6.5.x LTS release line.
  4. 4. Alternatively, upgrade to version 2026.5.0 or later for the newer release line.
  5. 5. After upgrade, verify that the vulnerable form fields no longer accept malicious script injection.
  6. 6. Validate that all custom components and integrations function correctly post-upgrade.
  7. 7. Deploy the tested upgrade to production environment.
Caveat Standard AEM upgrade considerations apply - review Adobe's upgrade documentation for compatibility notes on 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-47950 — 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-47950 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