dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-47053

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-16
Fix available
A fix is available. Upgrade to 6.5.23.0 / 2025.5 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 · moderate confidence

Adobe Experience Manager versions 6.5.22 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability where a low-privileged attacker can manipulate the DOM environment to execute malicious JavaScript in a victim's browser via a specially crafted web page.

MitigationUpgrade Adobe Experience Manager to version 6.5.23 or later to obtain the security patch, and implement strict Content Security Policy (CSP) headers to provide defense-in-depth against XSS attacks.

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

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 AEM product version via web console
    Navigate to the AEM Welcome page (typically at /libs/granite/core/content/login.html or the root of your AEM instance) and look for the version number displayed, or access Help > System Information > Products in the AEM interface
    Affected if The displayed version is older than 6.5.23.0 or falls in the 2025.x line before 2025.5 (e.g., 2025.0 through 2025.4)
  2. Check AEM version via system console
    Access the System Information console at /system/console/systeminfo or /system/console/properties and locate the 'Adobe Experience Manager' version field
    Affected if The version shown is less than 6.5.23.0 or less than 2025.5 for the 2025.x release line
  3. Verify AEM author or publish instance is accessible
    Confirm that the AEM author instance (default port 4502) or publish instance (default port 4503) is reachable and exposes the AEM interface to users or attackers
    Affected if The AEM interface is network-accessible without compensating controls and the version check above shows a vulnerable version

You are affected if your installed Adobe Experience Manager version is below 6.5.23.0 (for 6.5.x releases) or below 2025.5 (for 2025.x releases) and the AEM web interface is accessible to users or untrusted parties.

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 or later
Fixed in 6.5.23.02025.5
Interim mitigation

Upgrade Adobe Experience Manager to version 6.5.23 or later to obtain the security patch, and implement strict Content Security Policy (CSP) headers to provide defense-in-depth against XSS attacks.

Recommended fix High confidence

AEM 6.5.23.0 (for 6.x track) or 2025.5 (for cloud-native/flexible packaging)

  1. Verify current Adobe Experience Manager version by checking the AEM welcome page or system console
  2. Review the Adobe Experience Manager 6.5.23.0 or 2025.5 release notes for changes and deprecations
  3. Create a full backup of the AEM repository (segment store, datastore, and database)
  4. Perform a staging environment upgrade to validate compatibility with custom code and configurations
  5. Execute the upgrade following Adobe's official documentation for your deployment type (JAR or EAR)
  6. After upgrade, verify all custom bundles, applications, and integrations function correctly
  7. Validate that the XSS vulnerability is resolved by testing for proper DOM sanitization
Caveat Review release notes for potential breaking changes; test thoroughly in non-production first as custom components, overlays, or third-party integrations may require updates after the upgrade

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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