dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-47951

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. When victims browse to pages containing these compromised fields, the malicious script executes in their browsers. The scope change indicates the vulnerability impacts resources beyond the vulnerable component itself.

MitigationApply Adobe's security patch for AEM versions 6.5.24, LTS SP1, or 2026.04 and later. Additionally, implement robust input validation and output encoding on all form fields to prevent script injection.

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. Determine AEM product version
    Access the AEM system information console or check the version file in the installation directory to identify the exact installed version
    Affected if The installed version is earlier than 6.5.25.0, earlier than 2026.5.0, or matches version 6.5 (6.5.24 and earlier, LTS SP1, 2026.04 and earlier)
  2. Identify if Forms module is enabled
    Review the AEM Forms configuration through the Felix console or forms endpoint to determine if the Forms feature is installed and active
    Affected if Forms module is enabled and form creation is permitted in the environment
  3. Inspect form field validation settings
    Examine the form field definitions within AEM Forms through the form editor or configuration to verify whether input validation rules and output encoding are applied to user-editable form fields
    Affected if Form fields do not have input validation or output encoding/sanitization configured
  4. Check Content Security Policy configuration
    Review the dispatcher configuration or web server settings to inspect whether CSP headers are defined and whether they restrict inline script execution
    Affected if CSP headers are missing or configured to allow inline scripts (script-src 'unsafe-inline')

The environment is affected if running a vulnerable AEM version (before 6.5.25.0 or 2026.5.0) and Forms are in use without proper input validation and output encoding on form fields accessible to low-privilege users

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 Adobe's security patch for AEM versions 6.5.24, LTS SP1, or 2026.04 and later. Additionally, implement robust input validation and output encoding on all form fields to prevent script injection.

Recommended fix High confidence

Upgrade to AEM 6.5.25.0 (for 6.5.x branch) or 2026.5.0 (for 2026.x branch)

  1. Review Adobe Experience Manager release notes for version 6.5.25.0 or 2026.5.0 to understand changes and prerequisites
  2. Create a full backup of the current AEM instance including repository, database, and configurations
  3. Set up a staging environment mirroring production to test the upgrade
  4. Stop the AEM instance and run the upgrade to version 6.5.25.0 (for 6.5.x branches) or 2026.5.0 (for 2026.x branches)
  5. Verify all custom workflows, integrations, and third-party plugins are compatible with the new version
  6. Test the fix by attempting to inject malicious scripts into form fields to confirm XSS is mitigated
  7. Deploy the validated upgrade to production environment
Caveat Point releases typically have minimal breaking changes but thorough testing of custom components and integrations is recommended before production deployment

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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