CVE-2025-46857
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 reflected Cross-Site Scripting (XSS) vulnerability. If a low privileged attacker is able to convince a victim to visit a URL referencing a vulnerable page, malicious JavaScript content may be executed within the context of the victim's browser.
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 reflected Cross-Site Scripting (XSS) vulnerability. The flaw allows a low-privileged attacker to inject malicious JavaScript into URL parameters, which gets reflected back in the server response and executed within the victim's browser context.
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.
-
Check AEM version via About pageNavigate to /libs/granite/core/content/about.html or access the Help menu > About Adobe Experience Manager in the AEM console to view the installed version numberAffected if The displayed version is 6.5.22 or earlier, or falls below 2025.5.0 (for year-based releases)
-
Check version via System ConsoleAccess /system/console/about to retrieve the precise AEM version details including the build numberAffected if Version shown is less than 6.5.23.0 or less than 2025.5.0
-
Verify user-accessible endpointsIdentify any publicly or internally accessible AEM pages that accept URL parameters (query strings), as these are the potential vectors for reflected XSSAffected if Any user-accessible endpoint accepts and reflects URL parameter values back in the response without encoding
You are affected if your installed AEM version is below 6.5.23.0 (for 6.5.x releases) or below 2025.5.0 (for year-based releases) and you have user-accessible endpoints that reflect URL parameters in responses.
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
Apply Adobe's security patch by upgrading to AEM 6.5.23 or later. Additionally, implement output encoding on user-supplied inputs and configure Content Security Policy headers to mitigate XSS risks.
6.5.23.0 (for 6.5.x line) or 2025.5.0 (for newer release line)
- Upgrade Adobe Experience Manager to version 6.5.23.0 or later for the 6.5.x release line
- If using the newer release cadence (2024.x/2025.x), upgrade to version 2025.5.0 or later
- After upgrading, verify the fix by testing that the reflected XSS vulnerability is no longer present in the application
- Ensure standard post-upgrade validation is performed to confirm all functionalities work correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46857 — 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-46857 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