dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46870

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 6.5.23.0 / 2025.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.22 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.

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.22 and earlier contain a stored Cross-Site Scripting vulnerability in form fields. A low-privileged attacker can inject malicious JavaScript into form inputs, which persists on the server and executes in victims' browsers when they view the affected page.

MitigationApply the vendor patch or upgrade to a fixed version of AEM (6.5.23 or later). Implement output encoding on form fields and consider Content Security Policy headers to mitigate XSS execution.

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.23.0< 2025.5.0

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. Check Adobe Experience Manager version
    Navigate to AEM Welcome page > Tools > Operations > Diagnosis, or check the version.properties file in the crx-quickstart folder. You can also access /system/console/bundles to view the AEM core bundle version.
    Affected if Installed version is below 6.5.23.0 for 6.x releases, or below 2025.5.0 for cloud/2025 releases
  2. Identify form field components in use
    Review the AEM instance for use of form components such as Adaptive Forms, Core Form components (form-text, form-hidden, form-checkbox), or custom form implementations in /apps or /content.
    Affected if The instance uses form input components that accept user-generated content
  3. Search for stored XSS payloads in form data
    Use AEM Query Builder or CRXDE Lite to search nodes under /content for suspicious script tags in form field values. Example query: path=/content type=nt:unstructured property=jcr:content property.value=%3Cscript%3E
    Affected if Malicious JavaScript payloads are found persisted in form field repository nodes
  4. Review form field input validation
    Inspect the form component's edit dialog configuration (dialog.xml or .xml) under /apps for missing input validation rules or client-side libraries that perform output encoding.
    Affected if Form components lack server-side input validation or output encoding is not applied to stored values

You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 and the system uses form fields that accept user input 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.23.0 / 2025.5.0 or later
Fixed in 6.5.23.02025.5.0
Interim mitigation

Apply the vendor patch or upgrade to a fixed version of AEM (6.5.23 or later). Implement output encoding on form fields and consider Content Security Policy headers to mitigate XSS execution.

Recommended fix High confidence

AEM 6.5.23.0+ (6.x line) or 2025.5.0+ (Cloud Service)

  1. Backup your AEM instance and database before proceeding with any upgrade
  2. Review the Adobe Experience Manager 6.5.23 release notes and migration guide at helpx.adobe.com for any specific migration requirements
  3. For AEM 6.5.x users: Upgrade to version 6.5.23.0 or later
  4. For AEM as a Cloud Service users: Upgrade to version 2025.5.0 or later
  5. After upgrade, verify the XSS protection filters are working correctly by testing form field inputs
  6. Test critical workflows and templates to ensure functionality is preserved post-upgrade
Caveat Point releases typically have minimal breaking changes but always review release notes for any configuration or API changes

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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