CVE-2025-46887
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 in form fields. A low-privileged attacker can inject malicious JavaScript into vulnerable form input fields, which executes when other users view the affected page.
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 versionAccess the AEM Welcome page or use the system console (/system/console/bundles) to identify the exact version number of Adobe Experience Manager installed in your environment.Affected if The installed version is 6.5.22 or earlier, or falls below 2025.5.0, meaning it falls within the vulnerable version range.
-
Verify Forms feature is enabledCheck if Adobe Experience Manager Forms modules are installed and enabled in your AEM instance by reviewing the package manager or installed applications.Affected if AEM Forms is installed and active, creating the attack surface for the vulnerable form input fields.
-
Identify exposed form endpointsReview your AEM instance for publicly or internally accessible form components, particularly Adaptive Forms, Core Components form containers, or custom form implementations at paths like /content/forms/af/.Affected if Form endpoints exist and accept user input without proper output encoding, allowing stored XSS to persist.
-
Audit form field input handlingInspect the form field components in your AEM Forms or Core Components implementation to determine if input validation and output encoding are implemented on the server side.Affected if Form fields accept and store unsanitized input, enabling malicious JavaScript to be stored in the form data repository.
-
Check for low-privileged user access to formsVerify whether low-privileged or anonymous users can submit forms and whether other users (including authors or administrators) can subsequently view the submitted content.Affected if Low-privilege users can submit forms and their submissions are rendered to other users without encoding, completing the exploit chain.
You are affected if your AEM installation version is below 6.5.23.0 or 2025.5.0 AND Forms are enabled with form fields that accept user input 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 Adobe Experience Manager to version 6.5.23 or later. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure until the patch can be applied.
AEM 6.5.23.0 or later, or AEM 2025.5.0 or later
- 1. Identify the current Adobe Experience Manager version in use (check /system/console/bundles or AEM startup logs)
- 2. Backup the current AEM instance including the repository, configuration, and any custom code
- 3. Download Adobe Experience Manager 6.5.23.0 or later from the official Adobe distribution portal (https://experience.adobe.com)
- 4. Install the upgrade following Adobe's official upgrade documentation for AEM 6.5 or the 2025.x release
- 5. After upgrade, verify the version number matches the fixed release (6.5.23.0 or 2025.5.0+)
- 6. Test the application functionality and specifically validate that user-supplied input in form fields is properly escaped
- 7. Clear AEM caches and rebuild any search indexes post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46887 — 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-46887 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