dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46856

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-20
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 DOM-based Cross-Site Scripting (XSS) vulnerability. A low privileged attacker could exploit this issue by manipulating the DOM environment to execute malicious JavaScript within the context of the victim's browser. Exploitation of this issue requires user interaction in that a victim must visit a specially crafted web page.

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 DOM-based Cross-Site Scripting (XSS) vulnerability. An attacker with low privileges can manipulate the DOM environment to inject and execute malicious JavaScript within a victim's browser session.

MitigationUpgrade Adobe Experience Manager to a version newer than 6.5.22, and implement Content Security Policy headers to mitigate DOM-based XSS vectors.

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. Confirm AEM is running in your environment
    Check for AEM processes (look for 'crx' or 'aem' in running processes) or access the AEM web console at /system/console (returns 200 if AEM is running)
    Affected if AEM is not present in your environment, you are not affected
  2. Determine the installed AEM version
    Access the AEM version information via the system console at /system/console/systeminfo or check the version.properties file in the AEM installation directory (typically in crx-quickstart/)
    Affected if Unable to retrieve version information, manual inspection required
  3. Compare your version against affected ranges
    Check if your installed version is less than 6.5.23.0 or less than 2025.5.0. Version format examples: 6.5.22.0, 2024.12.0, etc.
    Affected if Your version is < 6.5.23.0 or < 2025.5.0 - you are running a vulnerable version
  4. Identify custom components that manipulate the DOM
    Review any custom OSGi components or Sightly/JSP templates that use JavaScript to manipulate the DOM based on user-provided input (URL parameters, form data, or content from DAM/pages)
    Affected if Custom components exist that inject unsanitized user input directly into the DOM via innerHTML, eval(), or similar methods
  5. Check for existing Content Security Policy headers
    Inspect HTTP responses from your AEM instance for CSP headers (Content-Security-Policy) using browser dev tools or a curl command: curl -I https://your-aem-host
    Affected if No CSP headers are configured, the DOM XSS attack vector has no browser-side mitigation

You are affected if AEM is running and the installed version is either below 6.5.23.0 or below 2025.5.0, regardless of CSP header configuration.

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

Upgrade Adobe Experience Manager to a version newer than 6.5.22, and implement Content Security Policy headers to mitigate DOM-based XSS vectors.

Recommended fix High confidence

6.5.23.0 (for 6.x line) or 2025.5.0 (for newer release train)

  1. 1. Identify the current Adobe Experience Manager version in your environment
  2. 2. For AEM 6.x on-premise installations, plan upgrade to version 6.5.23.0 or later
  3. 3. For AEM cloud service or newer release trains, plan upgrade to version 2025.5.0 or later
  4. 4. Review Adobe's official upgrade documentation and release notes for the target version
  5. 5. Test the upgrade in a non-production environment first
  6. 6. Perform the upgrade following Adobe's recommended procedures
  7. 7. Verify the DOM-based XSS vulnerability is remediated through testing
  8. 8. Deploy the upgraded version to production
Caveat Always review release notes for potential compatibility changes before upgrading production systems

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-2025-46856 — 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-46856 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