CVE-2025-46891
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 vulnerability where low-privileged users can inject malicious JavaScript into form fields. When other users browse to pages containing these compromised fields, the malicious script executes in their browsers, potentially allowing 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.
-
Determine the installed AEM versionAccess the AEM About page (Help > About Adobe Experience Manager) or check the version.properties file in the crx-quickstart directoryAffected if The version shown is earlier than 6.5.23.0 or earlier than 2025.5.0 (for cloud/2025 releases)
-
Identify if low-privileged users can access form authoringReview the user group permissions in AEM Assets or Sites admin console. Check if groups such as 'contributors' or custom groups with limited privileges have Create or Modify permissions on content pages containing form componentsAffected if Users with limited (non-admin) privileges can create or edit content in pages that contain form fields
-
Audit existing form field content for suspicious scriptsSearch the content repository (via CRXDE Lite or a content query) for form component nodes under /content and examine string values for script tags, javascript: URIs, or event handler attributes like onerror, onloadAffected if Any form field content contains HTML script tags, JavaScript URIs, or event handler attributes that could execute malicious code
-
Review form component configuration for unconstrained inputExamine the Edit dialog configuration of form components (form fields, text fields, text areas) in the Touch UI or Classic UI dialog definition XML files under /apps. Check if there are restrictions on allowed input patternsAffected if Form field components lack input validation constraints or regex patterns in their dialog configuration
Your environment is affected if the installed AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privileged users can author content in form-enabled pages.
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 Adobe Experience Manager to version 6.5.23 or later. Additionally, implement input validation and output encoding for all form fields as a defense-in-depth measure.
AEM 6.5.23.0 (6.5.x line) or AEM as a Cloud Service 2025.5.0+
- Identify your current Adobe Experience Manager version by checking /system/console/configMgr or the product welcome page
- If running AEM 6.5.x line: plan upgrade to version 6.5.23.0 or later
- If running AEM as a Cloud Service: plan upgrade to version 2025.5.0 or later
- Schedule upgrade during planned maintenance window following Adobe's upgrade documentation
- After upgrade, verify the fix by testing form fields for XSS payload injection (e.g., <script>alert(1)</script>)
- Confirm malicious scripts are no longer executed when viewing content containing the payload
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46891 — 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-46891 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