CVE-2025-65923
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 · uneditedA Stored Cross-Site Scripting (XSS) vulnerability was discovered within the CSV import mechanism of ERPNext thru 15.88.1 when using the Update Existing Recordsoption. An attacker can embed malicious JavaScript code into a CSV field, which is then stored in the database and executed whenever the affected record is viewed by a user within the ERPNext web interface. This exposure may allow an attacker to compromise user sessions or perform unauthorized actions under the context of a victim's account.
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 XSS vulnerability in ERPNext's CSV import mechanism allows attackers to embed malicious JavaScript in CSV fields when using the 'Update Existing Records' option. The unsanitized payload persists in the database and executes whenever users view the affected records, enabling session hijacking or unauthorized actions.
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<= 15.88.1CVSS 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 ERPNext installationRun command: bench version or check Frappe/ERPNext version via the web interface (Bench > Help > About)Affected if Installed version is 15.88.1 or lower
-
Verify CSV import usageReview access logs or user activity for the CSV Import tool (Data Tools > Import or /api/method/frappe.core.doctype.data_import.data_import.upload), especially look for imports using the 'Update Existing Records' option enabledAffected if CSV imports with 'Update Existing Records' option have been performed
-
Inspect database for suspicious contentQuery the database for records in DocType tables that contain script tags, event handlers (onerror, onload, onclick), or javascript: URIs in text fields. For example: SELECT name, modified FROM `tabItem` WHERE item_code LIKE '%<script%' OR item_code LIKE '%onerror=%'Affected if Any records contain unsanitized HTML/JavaScript payloads, particularly in fields commonly imported via CSV
-
Check for unauthorized actionsReview Activity Log (System > Log > Activity Log) and access logs for unusual script execution or session anomalies around the time of CSV importsAffected if Unexpected script execution or anomalous user actions are logged after CSV imports were performed
User is affected if running ERPNext version 15.88.1 or lower AND has used CSV import with 'Update Existing Records' enabled, with malicious payloads persisting in database records.
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 · scopedImplement output encoding and input validation on all CSV field data during import, especially when updating existing records. Apply context-aware escaping before rendering data in the web interface.
ERPNext version 15.89.0 or later
- 1. Backup your ERPNext database and files before performing any upgrade.
- 2. Update ERPNext to version 15.89.0 or later using the bench update command: bench update --patch
- 3. After updating, verify the CSV import functionality works correctly with the Update Existing Records option.
- 4. Clear the application cache: bench clear-cache
- 5. Test that HTML entities are properly escaped when importing CSV files with special characters.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65923 — 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-65923 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