CVE-2025-46880
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privilege users to inject malicious JavaScript into form fields. The malicious payload persists on the server and executes in victims' browsers when they 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.
-
Verify AEM versionAccess the AEM About page (navigate to /system/console/bundles or use the Help menu > About Adobe Experience Manager) to determine the installed version numberAffected if The installed version is earlier than 6.5.23.0 (for 6.x releases) or earlier than 2025.5.0 (for Cloud releases)
-
Confirm AEM Forms or Adaptive Forms module is activeCheck if AEM Forms is enabled by navigating to the Forms section in the AEM console or reviewing installed bundles related to forms.forms-coreAffected if The Forms module is installed and active in the AEM environment
-
Identify low-privilege user access to form authoringReview user group permissions in AEM at Tools > Security > Permissions. Check if standard users or custom groups with limited privileges have access to create or edit adaptive forms or form fragmentsAffected if Low-privilege users (non-admin) have permissions to author or edit form fields
-
Inspect form field input validation settingsReview the XML configuration or JSON definition of adaptive form fields in the CRX/DE repository under /content/forms/af to check for input validation and output encoding settingsAffected if Form fields lack server-side input validation or output encoding is disabled
-
Audit recent form submissions for suspicious contentQuery form submission data in the AEM repository (under /content/forms/submissions or the associated data store) for patterns like script tags, javascript: URLs, or event handler attributesAffected if Form submission records contain unencoded HTML or script tags
The environment is likely affected if AEM version is below 6.5.23.0 or below 2025.5.0 AND the Forms module is enabled with low-privilege users having form authoring access.
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
Update AEM to version 6.5.23 or later per Adobe's official patch. Additionally, implement output encoding on form fields and consider Content Security Policy headers as defense-in-depth.
AEM 6.5.23.0 or later / AEM as a Cloud Service 2025.5.0 or later
- 1. Identify the current Adobe Experience Manager version installed in the environment
- 2. For AEM 6.5.x installations: Upgrade to version 6.5.23.0 or later
- 3. For AEM as a Cloud Service installations: Upgrade to version 2025.5.0 or later
- 4. After upgrade, verify the XSS vulnerability is resolved by testing form field inputs
- 5. Clear browser cache and test that malicious scripts are no longer executed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46880 — 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-46880 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