CVE-2025-46866
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 · moderate confidenceStored XSS vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged users to inject malicious JavaScript into form fields that execute when other users view the affected pages.
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 installed AEM versionNavigate to the AEM Welcome page or access the system information via the Help menu, or query the version using the OSGi component com.adobe.granite.packaging.internal.AEMPackage at /system/console/status-productinfo, or check the version.properties file in the crx-quickstart folderAffected if The installed version is earlier than 6.5.23.0 (for AEM 6.5.x releases) or earlier than 2025.5.0 (for the 2025 release line)
-
Identify AEM Forms or custom form components in useReview the content structure in CRXDE Lite under /content or /apps for nodes related to form components (look for cq:component types containing 'form', 'textfield', 'textarea', or similar form elements)Affected if AEM Forms adaptive components or custom form field components are deployed and accessible to low-privilege users
-
Audit form field node configurations for unsanitized input patternsIn CRXDE Lite, examine the XML or properties of form field nodes (under /apps or /content) and inspect the name, value, title, and placeholder attributes for any script tags or JavaScript event handlersAffected if Form field definitions contain raw user-supplied values in attributes without proper encoding or input validation
-
Review content pages with form submissions for malicious payloadsQuery the repository via CRXDE Lite or the Query tool (XPath or SQL) for form-related content nodes containing script tags, javascript:, or on* event handlers in text fieldsAffected if Stored XSS payloads (script tags, event handlers) are found embedded in form field content nodes
-
Check audit and access logs for low-privilege form submissionsExamine the AEM error.log and access.log files (or the Audit Log in the Tools console) for POST requests to form endpoints from low-privilege users containing suspicious patterns like <script> or javascript:Affected if Low-privilege users have submitted form content containing script injection patterns
You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND you have form components that accept user input and are accessible to low-privileged 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
Upgrade to a patched AEM version and implement input validation with output encoding on all form fields to prevent script injection.
AEM 6.5.23.0 (on-premise) or AEM as a Cloud Service 2025.5.0
- 1. Back up the AEM repository (Oak repository) and database before starting any upgrade
- 2. Test the upgrade in a non-production environment first (staging/dev)
- 3. For AEM 6.5.x on-premise: Install AEM Service Pack 6.5.23 or later via the Package Manager or CRXDE
- 4. For AEM as a Cloud Service: Ensure the deployment pipeline uses the 2025.5.0 release or later
- 5. After upgrade, verify the form fields that were vulnerable are no longer susceptible to stored XSS
- 6. Clear AEM caches and rebuild any indexes if required post-upgrade
- 7. Verify all custom code and integrations still function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46866 — 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-46866 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