CVE-2025-47049
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. An 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 confidenceAdobe Experience Manager versions 6.5.22 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability. The issue stems from improper handling of DOM manipulation, allowing attackers to inject malicious JavaScript that executes within the victim's browser context. Exploitation requires tricking a user into visiting a specially crafted web page.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Locate the installed AEM versionAccess the AEM Welcome page (main URL) or go to Help > About Adobe Experience Manager. Alternatively, check the version.properties file in the crx-quickstart folder or query the system via the JMX console at /system/console/jmx/com.adobe.granite%3Aversion%3D1Affected if The version displayed is 6.5.22 or earlier, or falls below 2025.5.0 (such as 2024.x releases)
-
Confirm the exact version numberNote the full version string (for example, 6.5.21.0 or 2024.3.0). AEM uses two numbering schemes: 6.5.x for the long-term support line and a year-based format (YYYY.x) for feature releasesAffected if The version starts with 6.5 and the minor version is 22 or lower, or the version begins with a year lower than 2025 (such as 2024, 2023, etc.)
-
Identify the AEM release channelCheck if the instance follows the 6.5.x LTS channel or the yearly feature release channel (2024.x, 2025.x, etc.) by reviewing the version string format and your internal release documentationAffected if The instance is on the 6.5.x LTS track at version 6.5.22 or below, or on any yearly release below 2025.5.0
-
Verify if user-facing web content is renderedDetermine if the AEM instance serves published web content to end users via AEM Sites, Forms, or community features. Check for published content pages accessible without authenticationAffected if The instance exposes published web content to users, as DOM-based XSS requires a victim to browse a crafted page
-
Check for Content Security Policy deploymentReview the web server or CDN configuration, or check AEM's org.apache.sling.security.impl.ReferrerFilter OSGi configuration, for CSP header presence. Use browser developer tools to inspect response headers on published pagesAffected if No CSP headers are present, as this indicates a missing compensating control that could mitigate XSS impact
-
Audit custom components using DOM APIsReview any custom AEM components, HTL templates, or client-side JavaScript for direct DOM manipulation (innerHTML, insertAdjacentHTML, document.write, etc.) without sanitization. Search code repositories for these patternsAffected if Custom code directly inserts request parameters or user data into the DOM without encoding
You are affected if your AEM installation shows version 6.5.22 or earlier, or any version below 2025.5.0, and the instance serves published web content to users without compensating controls like CSP headers.
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 Adobe Experience Manager to version 6.5.23 or later. Additionally, implement Content Security Policy (CSP) headers and ensure all user-supplied data is properly sanitized before being inserted into the DOM.
Adobe Experience Manager 6.5.23.0 or later (6.5.x line); Adobe Experience Manager 2025.5.0 or later (cloud/2025 line)
- 1. Back up the current Adobe Experience Manager instance and verify data integrity
- 2. Review Adobe's official upgrade documentation for your deployment type (6.5.x on-premise or cloud service)
- 3. For on-premise 6.5.x installations: Upgrade to Adobe Experience Manager 6.5.23.0 or later
- 4. For cloud-based deployments: Upgrade to Adobe Experience Manager 2025.5.0 or later
- 5. After upgrade, verify the DOM-based XSS vulnerability is resolved by testing with the fixed version
- 6. Validate that custom code and integrations function correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47049 — 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-47049 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