Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-65923: n/a

0
Medium
VulnerabilityCVE-2025-65923cvecve-2025-65923
Published: Tue Feb 03 2026 (02/03/2026, 00:00:00 UTC)
Source: CVE Database V5

Description

A 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.

AI-Powered Analysis

AILast updated: 02/04/2026, 08:10:45 UTC

Technical Analysis

CVE-2025-65923 is a stored Cross-Site Scripting (XSS) vulnerability identified in the CSV import mechanism of ERPNext, a widely used open-source enterprise resource planning (ERP) system. The vulnerability specifically arises when the 'Update Existing Records' option is used during CSV imports. An attacker can craft a CSV file containing malicious JavaScript code embedded within one or more fields. When this CSV is imported, the malicious script is stored persistently in the ERPNext database. Subsequently, whenever a user accesses the affected record through the ERPNext web interface, the embedded script executes in the context of the user's browser session. This execution can lead to session hijacking, enabling the attacker to impersonate the user, steal sensitive information, or perform unauthorized actions such as modifying data or escalating privileges within the ERP system. The vulnerability does not require the attacker to have prior authentication to inject the payload, but the victim must view the compromised record for the exploit to trigger. No CVSS score has been assigned yet, and no known public exploits have been reported. The lack of a patch or mitigation details in the provided information suggests that organizations should proactively implement input validation and restrict CSV import permissions to trusted users. Given ERPNext's role in managing critical business functions like inventory, finance, and human resources, exploitation could have significant operational and data confidentiality impacts.

Potential Impact

For European organizations, this vulnerability poses a substantial risk due to ERPNext's use in managing sensitive business operations. Successful exploitation could lead to unauthorized access to confidential corporate data, manipulation of financial records, or disruption of business processes. The ability to hijack user sessions or perform actions under a victim's account increases the risk of insider-like attacks without direct insider involvement. This could result in data breaches, regulatory non-compliance (e.g., GDPR violations), financial losses, and reputational damage. Organizations relying heavily on CSV imports for bulk updates are particularly vulnerable. Additionally, sectors such as manufacturing, logistics, and public administration that depend on ERPNext for critical workflows may face operational disruptions. The absence of known exploits in the wild provides a window for mitigation, but the potential impact remains high if exploited.

Mitigation Recommendations

1. Immediately restrict CSV import functionality to trusted, authenticated users with a clear need to perform bulk updates. 2. Implement strict input validation and sanitization on all CSV fields before importing data into ERPNext, ensuring that scripts or HTML tags are neutralized or rejected. 3. Monitor ERPNext logs for unusual import activities or unexpected changes in records that could indicate exploitation attempts. 4. Educate users to be cautious when viewing records recently updated via CSV imports, especially if imported by less trusted sources. 5. Apply ERPNext updates and patches promptly once the vendor releases a fix addressing this vulnerability. 6. Consider deploying web application firewalls (WAFs) with rules to detect and block XSS payloads targeting ERPNext interfaces. 7. Conduct regular security assessments and penetration tests focusing on import functionalities and user privilege configurations. 8. Enforce the principle of least privilege for ERPNext users to limit the impact of compromised accounts.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-11-18T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6982fcd3f9fa50a62f7662fd

Added to database: 2/4/2026, 8:01:23 AM

Last enriched: 2/4/2026, 8:10:45 AM

Last updated: 2/7/2026, 3:57:14 AM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats