CVE-2025-46852
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 payloads into vulnerable form inputs, which persist on the page and execute in the browsers of users who 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.
-
Identify AEM versionAccess the AEM Welcome page or check the product version via the system console (Navigate to Help > About Adobe Experience Manager or access /system/console/configMgr and look for version information)Affected if The installed version is earlier than 6.5.23.0 or earlier than 2025.5.0 (e.g., 6.5.22, 6.5.21, etc.)
-
Confirm form components are in useReview the AEM instance for any custom or out-of-the-box forms that collect user input (look for form containers, adaptive forms, or custom form components in the content structure under /content or /apps)Affected if The instance hosts form fields that accept and store user-submitted data without explicit output encoding validation in place
-
Test for input sanitization on form fieldsCreate or edit a form component and attempt to insert a benign XSS test payload such as <script>alert(1)</script> into a text input field, then save and view the rendered page source to see if the payload is reflected unescapedAffected if The payload appears in the rendered HTML as raw <script> tags rather than being HTML-encoded (e.g., as <script>)
A user is affected if their AEM version is below 6.5.23.0 or below 2025.5.0 AND the instance uses form fields that accept user input without proper sanitization, allowing stored XSS payloads to persist and execute.
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 AEM version 6.5.23 or later. Additionally, implement output encoding and input validation/sanitization on all form fields to prevent XSS execution.
Adobe Experience Manager 6.5.23.0 or later, or 2025.5.0 or later
- 1. Identify the current Adobe Experience Manager version in use (6.5.22 or earlier, or a version before 2025.5.0)
- 2. Schedule a maintenance window for the upgrade process
- 3. Backup the AEM instance including the repository, configuration, and any custom code
- 4. Review Adobe's release notes for version 6.5.23.0 (or 2025.5.0) to understand any specific migration requirements
- 5. Upgrade Adobe Experience Manager to version 6.5.23.0 or later (for 6.x line), or to version 2025.5.0 or later (for cloud/continuous release line)
- 6. After upgrade, verify that custom form components and fields function correctly
- 7. Test the application to confirm the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46852 — 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-46852 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