dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-47962

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 allowing low-privileged users to inject malicious JavaScript into form fields. The injected script executes when other users view pages containing the compromised fields. The scope changed due to the vulnerability impacting resources beyond the initially affected component.

MitigationUpdate Adobe Experience Manager to version 6.5.25, LTS SP2, or 2026.05 and later. Additionally, implement input validation and output encoding on form fields, and consider Content Security Policy headers to mitigate XSS risks.

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 the installed Adobe Experience Manager version
    Access the AEM System Information console at /system/console/status-productinfo or check the version.properties file in the crx-quickstart directory. Alternatively, query the JCR API for the version using a GET request to /bin/cq/versioninfo.json
    Affected if The version is less than 6.5.25.0, less than 2026.5.0, or falls within the 6.5.x family before the patched versions
  2. Verify if low-privilege users have access to Forms functionality
    Review user group permissions in AEM at /libs/granite/security/content/admin.html. Check if users assigned to 'contributor' or 'forms-user' groups can create or edit Adaptive Forms, Form Fragments, or Form Templates
    Affected if Low-privilege users (non-admin) can access and modify form creation interfaces or form field configurations
  3. Inspect custom form component code for output encoding
    Locate any custom form components or dialog XML files (/.apps/your-project/components) and examine the HTL (HTML Template Language) or JSP scripts rendering form field values. Look for context-aware encoding such as ${properties.fieldName @ context='html'} or equivalent encoding methods
    Affected if Form field values are rendered without proper context-aware output encoding (no @ context='html' or equivalent sanitization in HTL templates)
  4. Check Content Security Policy header configuration
    Navigate to AEM Felix Console at /system/console/config and locate the Adobe Granite HTML Library Manager configuration. Review the 'extraHeaders' or CSP-related configurations for script-src directives
    Affected if No CSP headers are configured or script-src is set to 'unsafe-inline' allowing arbitrary script execution from form inputs

You are affected if your AEM version is below 6.5.25.0 or 2026.5.0 AND low-privilege users can access form fields AND those fields render without output encoding or CSP protection.

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 Adobe Experience Manager to version 6.5.25, LTS SP2, or 2026.05 and later. Additionally, implement input validation and output encoding on form fields, and consider Content Security Policy headers to mitigate XSS risks.

Recommended fix High confidence

AEM 6.5.25.0 (LTS) or 2026.5.0 (2026 track)

  1. Back up the current Adobe Experience Manager instance and all content repositories
  2. Download Adobe Experience Manager 6.5.25.0 (for 6.5 LTS track) or 2026.5.0 (for the 2026 track) from the Adobe distribution center
  3. Install the new version in a staging or test environment
  4. Verify that the vulnerable form fields no longer allow script injection by testing with a benign XSS payload (e.g., <script>alert('XSS')</script>)
  5. Once validated, deploy the upgraded version to production
Caveat Review Adobe's release notes for 6.5.25.0 or 2026.5.0 for any breaking changes or migration requirements before upgrading

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
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA6.0 h
44.0 hours of engineering $7,680
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,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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