CVE-2026-12895 Frappe CVE debrief

Who should care

Defenders responsible for ERPNext and Frappe instances, security teams, and administrators should assess exposure and prioritize patching and monitoring. They should also restrict user privileges to prevent exploitation and monitor database activity for suspicious queries. Additionally, they should review compensating controls for exposed systems and track exceptions and retest remediated assets.

Why it matters

This SQL injection vulnerability in Frappe's ERPNext allows authenticated users with low privileges to execute arbitrary SQL queries, bypass access restrictions, and extract sensitive information. Defenders should prioritize verifying and patching vulnerable instances, restricting user privileges, and monitoring database activity.

• Authenticated users with low privileges can execute arbitrary SQL queries
• Bypass Frappe's access restrictions (DocPerm)
• Extract confidential information from the database, including fragments of the administrator's password hash
• Access sensitive data, such as credentials, integration tokens, or financial information

Technical summary

The vulnerability exists due to the application's use of direct string interpolation using `str.format()` without employing parameterized queries. This allows an authenticated user with low privileges to execute arbitrary SQL queries and bypass Frappe's access restrictions. The vulnerability affects ERPNext versions ERPNext 15.107.0 and Frappe 15.107.2. The application constructs SQL queries through direct string interpolation, allowing the name (docname) of a Supplier record containing SQL metacharacters to be interpreted as part of the query.

Defensive priority

Defenders should prioritize verifying and patching vulnerable ERPNext and Frappe instances, restricting user privileges, and monitoring for suspicious database activity.

Recommended defensive actions

• Verify and patch vulnerable ERPNext and Frappe instances
• Restrict user privileges to prevent exploitation
• Monitor database activity for suspicious queries
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the SQL injection vulnerability in Frappe's ERPNext. The Incibe CERT notice is also referenced. The vulnerability has been confirmed in ERPNext 15.107.0 and Frappe 15.107.2. Defenders should verify the patch status of their instances and restrict user privileges to prevent exploitation. Monitoring database activity for suspicious queries is also recommended. The source details are limited, so defenders should exercise caution and verify the information with the vendor or other trusted

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.