CVE-2025-46873
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 allowing low-privileged users to inject malicious JavaScript into form fields. When victims browse to pages containing these compromised fields, the injected scripts execute in their browsers.
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 Adobe Experience Manager versionNavigate to AEM Welcome page > Help > Version, or check the version.properties file in the installation directory. Alternatively, access the System Overview console at /system/console/vmstatAffected if The installed version is lower than 6.5.23.0 or lower than 2025.5.0
-
Identify form components accepting user inputReview the AEM instance for form components (Core Components, Adaptive Forms, or custom forms) that allow public or low-privileged user submissions. Check content pages for components like form, textfield, textarea that accept user data.Affected if Form components that accept user input are present and publicly accessible to low-privileged users
-
Inspect stored form data for XSS payloadsQuery the AEM repository (via CRXDE Lite at /crx/de or the Query Builder) for common XSS patterns in form field content nodes. Look for script tags, javascript: handlers, event attributes like onload/onerror, or encoded variants.Affected if Form submission nodes contain suspicious scripts, event handlers, or encoded payloads typical of XSS attacks
-
Verify low-privileged user access to formsReview user group permissions in AEM User Manager at /useradmin. Check if contributors, community members, or other low-privileged groups have create or modify permissions on form-containing content pages.Affected if Users with limited privileges (contributor level or below) can access and submit form fields
AEM is affected if the installed version is below 6.5.23.0 or below 2025.5.0 AND the environment contains form fields accessible to low-privileged users, or if malicious scripts are already stored in form submission data.
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. Alternatively, implement strict input validation and output encoding on all form fields to neutralize XSS payloads.
AEM 6.5.23.0 (on-premise) or AEM as a Cloud Service 2025.5.0/continuous release
- 1. Identify the current Adobe Experience Manager version by checking the product information in the AEM console or system/console/info
- 2. Create a complete backup of the AEM instance including content repository, configurations, and custom code
- 3. Schedule a maintenance window for the upgrade process
- 4. For AEM 6.5.x on-premise installations: Upgrade to version 6.5.23.0 or later
- 5. For AEM as a Cloud Service: Upgrade to version 2025.5.0 or later (or ensure the environment is on the latest continuous release)
- 6. After upgrade, verify the XSS vulnerability is resolved by testing form fields that previously accepted user input
- 7. Validate that all custom components and forms function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46873 — 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-46873 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