CVE-2025-46860
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 affecting form fields. A low-privileged authenticated attacker can inject malicious JavaScript into form inputs, which persists on the page and executes in victim users' browsers when they view the compromised 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.
-
Verify the installed Adobe Experience Manager versionAccess the AEM Welcome page and navigate to Help > About Adobe Experience Manager, or check the version manifest file in the installation directory. Compare the displayed version number against the affected ranges: versions earlier than 6.5.23.0 or earlier than 2025.5.0.Affected if The installed version is below 6.5.23.0 or below 2025.5.0
-
Identify user groups with form creation or editing permissionsIn AEM Tools, navigate to User Management or the Groups console. Review the permissions assigned to low-privilege user groups (such as authors or contributors) to determine if they have Create, Modify, or Delete permissions on form-related content nodes under /content/forms or similar form directories.Affected if Low-privileged authenticated users have permissions to create or edit form fields in the content repository
-
Inventory form fragments or adaptive forms using user-supplied inputsSearch the content repository for form components under /content/forms or use the Form Manager to list all published or draft forms. Identify forms that accept user input through text fields, text areas, or other input components.Affected if Form components that accept user input exist in the AEM instance and are accessible to low-privilege users
-
Inspect form field configuration for input validation settingsOpen a form in Form Editor or CRX/DE Lite and inspect individual form field components. Check the properties panel of input fields for validation patterns, input masks, or data type constraints. If validation is absent or minimal, the field accepts unsanitized input.Affected if Form input fields lack input validation constraints or allow unrestricted text input that could contain script tags
A user is affected if their AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privilege users can create or edit form fields without server-side input validation or output encoding enabled.
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. If immediate patching is not feasible, implement input validation and output encoding on form fields as a compensating control, and restrict low-privilege user permissions to form creation/editing.
6.5.23.0 (6.5.x line) or 2025.5.0 (cloud/continuous release)
- Review the Adobe Experience Manager 6.5.23.0 (6.5.x line) or 2025.5.0 (cloud/continuous release) release notes for changes and known issues
- Backup your current AEM instance and content repository before proceeding
- Test the upgrade in a staging or development environment before production deployment
- Upgrade Adobe Experience Manager to version 6.5.23.0 or higher (for 6.5.x on-premise/cloud customers)
- Upgrade to version 2025.5.0 or higher (for Adobe-managed cloud customers)
- Verify the stored XSS vulnerability is remediated by testing the affected form fields
- Deploy to production after successful validation
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-46860 — 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-46860 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