CVE-2025-47054
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 · uneditedAdobe 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 confidenceAdobe Experience Manager versions 6.5.22 and earlier contain a DOM-based Cross-Site Scripting vulnerability where a low-privileged attacker can manipulate the DOM environment to execute malicious JavaScript in a victim's browser. This requires user interaction via a specially crafted webpage.
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< 6.5.23.0< 2025.5.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed AEM versionAccess the AEM System Information console at /system/console/status-html or check the version.properties file in the crx-quickstart folderAffected if The installed version is below 6.5.23.0 or below 2025.5.0 (if on the 2025 release track)
-
Verify AEM release trackCheck whether the installation is on the 6.5.x LTS track or the 2025.yearly release track by examining the version stringAffected if Running AEM 6.5.x versions prior to 6.5.23.0, or any 2025.x version prior to 2025.5.0
-
Identify custom components handling DOM inputReview custom OSGi components or Sightly/JSP templates that read request parameters and write directly to the DOM using innerHTML, outerHTML, or document.write without sanitizationAffected if Custom components exist that perform unsanitized DOM manipulation of user-controlled input
-
Audit Content Security Policy headersInspect HTTP response headers for Content-Security-Policy or Content-Security-Policy-Report-Only on published instancesAffected if No CSP headers are configured, or CSP allows unsafe-inline which reduces defense-in-depth against DOM XSS
Your environment is affected if running Adobe Experience Manager versions 6.5.x prior to 6.5.23.0 or 2025.x prior to 2025.5.0, especially if custom components perform DOM manipulation with user input without CSP protection.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.5.23.02025.5.0
Upgrade to AEM 6.5.23 or later if available. Additionally, implement strict Content Security Policy (CSP) headers and ensure all DOM manipulations properly sanitize and encode user-controlled input.
AEM 6.5.23.0 or later; AEM Cloud 2025.5.0 or later
- 1. Review the current Adobe Experience Manager version installed in your environment
- 2. For AEM 6.5.x installations: Upgrade to version 6.5.23.0 or later
- 3. For AEM cloud installations: Upgrade to version 2025.5.0 or later
- 4. Verify the upgrade in a non-production environment before deploying to production
- 5. Test critical workflows and custom integrations post-upgrade to ensure compatibility
- 6. Deploy the upgraded version to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47054 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47054 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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