CVE-2025-46953
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. Scope is changed.
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 confidenceA stored Cross-Site Scripting vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged authenticated users to inject malicious JavaScript into form fields. When other users view pages containing these compromised fields, the malicious script executes in their browsers, enabling session hijacking, defacement, or data theft.
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.
-
Identify AEM versionAccess the AEM welcome page or check the product version through the system information console (typically at /system/console/bundles or via the About Adobe Experience Manager option in the help menu)Affected if The installed version is 6.5.22 or earlier, or any version below 2025.5.0 for the newer release line
-
Confirm Forms module is in useReview your AEM instance for adaptive forms, form fragments, or form containers that accept user input. Check content structures under /content/forms for form assetsAffected if Forms that accept user input are published and accessible to authenticated users
-
Verify low-privileged user accessReview user group assignments and permissions in AEM under Tools > Security > Users or Groups. Confirm that users with contributor-level or limited permissions can create or edit form contentAffected if Low-privileged authenticated users have permission to author or edit form fields
-
Inspect form content for injected scriptsSearch form field definitions and submitted data in CRX/DE (accessible at /crx/de) under /content/forms for script tags, javascript: URIs, or event handler attributes in field valuesAffected if Form fields contain unsanitized script tags, event handlers, or JavaScript URIs in field values or metadata
-
Review published page renderingAccess published forms as a standard user would and inspect the HTML source of rendered form fields to verify if user-supplied values are properly escapedAffected if User-supplied values render as raw HTML or execute as script when the form is viewed
Your environment is affected if you are running AEM below version 6.5.23.0 or below 2025.5.0 AND your forms accept user input from low-privileged authenticated users.
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 the official Adobe security patch for AEM 6.5.22 and earlier; review and harden form field input validation and output encoding; implement Content Security Policy headers to mitigate XSS execution.
AEM 6.5.23.0 or later; or AEM as a Cloud Service 2025.5.0 or later
- Identify your current Adobe Experience Manager version by checking the product about page or system console
- For AEM 6.5.x users: Upgrade to version 6.5.23.0 or later
- For AEM as a Cloud Service users: Upgrade to version 2025.5.0 or later
- After upgrading, verify that the form fields where the XSS was previously possible no longer allow script injection
- Test the fix by attempting to submit forms with malicious script content and confirming they are sanitized or blocked
- Review user permissions and implement least-privilege principles for form field access
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-46953 — 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-46953 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