CVE-2025-46957
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. The injected payload persists on the page and executes in victim browsers when they view the affected content.
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 versionNavigate to the AEM Welcome page or access the system information via the Felix console at /system/console/bundles, or check the version.properties file in the crx-quickstart folderAffected if The version is below 6.5.23.0 or below 2025.5.0
-
Verify AEM platform release typeCheck whether the installation is on the 6.5.x LTS track or the 2025 quarterly release track by reviewing the version number format in the AEM About page (Help > About Adobe Experience Manager)Affected if Running any 6.5.x version before 6.5.23.0, or any 2025 release before 2025.5.0
-
Identify custom form componentsReview the /apps directory in CRX/DE (accessible at /crx/de) for custom form field components or Granite UI form widgets that may handle user input without output encodingAffected if Custom form components exist that accept user input without proper encoding
-
Audit recent form submissionsQuery the repository for content created by users with low-level permissions (such as those assigned to the 'content-author' or 'community-member' groups) in form-enabled content pages, reviewing the cq:acUUID or data attributes stored in the content nodesAffected if Form content exists that was authored by low-privileged users and contains unsanitized field values
You are affected if your AEM version is below 6.5.23.0 (6.5.x track) or below 2025.5.0 (2025 track) AND your system hosts form fields that accept input from low-privileged users without output encoding.
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 a version newer than 6.5.22. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure.
AEM 6.5.23.0 or later, or AEM as a Cloud Service release 2025.5.0 or later
- Download Adobe Experience Manager version 6.5.23.0 or later from the official Adobe distribution channel (software.adobe.com)
- Alternatively, upgrade to version 2025.5.0 or later if using the newer release cadence
- Follow the standard AEM upgrade procedure: stop the AEM instance, backup the repository, run the upgrade installer, validate the upgrade, and restart the instance
- After upgrade, verify that the vulnerable form fields no longer accept malicious script injection
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46957 — 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-46957 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