CVE-2025-46960
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 stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.
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 stored Cross-Site Scripting (XSS) vulnerability. A low-privilege attacker can inject malicious JavaScript into form fields, which persists in the system. When victims browse to pages containing the compromised fields, the malicious script executes in their browsers, potentially stealing session cookies or performing actions on behalf of the user.
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 your Adobe Experience Manager versionAccess the AEM welcome page or system console to view the installed version number. Compare this version against the affected ranges: versions before 6.5.23.0 or before 2025.5.0.Affected if The installed version is less than 6.5.23.0 or less than 2025.5.0
-
Verify if low-privilege user creation is enabledCheck if the AEM instance allows creation of low-privilege or contributor-level user accounts, as this is required for the attacker to inject the malicious script.Affected if Low-privilege users can be created or the instance has contributor authors with form input access
-
Inspect form fields for stored XSS payloadsReview content in form-based workflows, user profiles, comment fields, or any user-submitted text fields for suspicious patterns such as script tags, javascript: URIs, or event handlers like onload/onerror.Affected if Any form fields contain unencoded script tags or javascript: protocols
-
Check recent content modifications for malicious scriptsReview audit logs or content change history for recent entries involving form submissions that contain JavaScript code or HTML tags in text fields.Affected if Recent content updates include script tags or JavaScript in fields that should only contain plain text
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privilege users can submit form content that accepts raw HTML or script tags.
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 Adobe Experience Manager version 6.5.23 or later which contains the security patch. Additionally, implement input validation and output encoding for all form fields to prevent XSS injection.
6.5.23.0 (6.5.x line) or 2025.5.0 (2025 line)
- Upgrade Adobe Experience Manager to version 6.5.23.0 or later if running 6.5.x line
- Or upgrade to version 2025.5.0 or later if running the newer release line
- After upgrade, verify the XSS fix is applied by testing form fields that previously accepted arbitrary scripts
- Confirm no regression in custom components after upgrading
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46960 — 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-46960 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