CVE-2025-46910
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 Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privilege attackers to inject malicious JavaScript into form fields. When other users view pages containing these compromised fields, the injected scripts execute in their browsers, enabling session hijacking, credential theft, or defacement.
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 Adobe Experience Manager versionAccess the AEM Welcome page or check the product.info via the system console (navigate to /system/console/products or check the About Adobe Experience Manager dialog from the top-left menu)Affected if The installed version is below 6.5.23.0 or below 2025.5.0
-
Confirm AEM Forms module is in useCheck if Adaptive Forms, Foundation Forms, or Core Components with forms are enabled by navigating to the Forms section in AEM Assets or checking the /aem/forms existence in the repositoryAffected if Forms functionality is present and users can create or edit form content
-
Verify low-privilege user access to formsReview user/group permissions in AEM User Management (navigate to /security/users or /security/groups) and check if non-admin users have create, modify, or contributor access to form content or Adaptive FormsAffected if Low-privilege users (contributors, authors, or custom groups with limited permissions) can access and modify form fields or form content
-
Inspect form field input handlingReview form configurations in AEM Forms (check Adaptive Form templates and form models at /conf or /apps) to confirm if custom form field components are accepting unvalidated user inputAffected if Form fields exist that accept user input without visible input validation or output encoding configured
You are affected if your AEM installation version is below 6.5.23.0 or below 2025.5.0, Forms are enabled, and low-privilege users can inject content into form fields that are rendered to other users without proper encoding.
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 Adobe Experience Manager version 6.5.23 or later. Additionally, implement input validation and output encoding for all form fields to prevent XSS attacks.
AEM 6.5.23.0 or later; or AEM 2025.5.0 or later
- 1. Review Adobe Experience Manager upgrade documentation at helpx.adobe.com for your current version
- 2. Perform a full backup of your AEM instance including content repository and configuration
- 3. Test the upgrade in a staging environment before applying to production
- 4. Upgrade AEM 6.5.x to version 6.5.23.0 or later, OR upgrade to 2025.5.0 or later for the newer release line
- 5. Verify the upgrade was successful and all services are running
- 6. Validate that the XSS vulnerability is resolved by testing form field inputs with malicious scripts
- 7. Monitor for any post-upgrade issues in production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46910 — 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-46910 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