CVE-2025-11461: Frappe CRM · SQL Injection
Affects Frappe CRMSource CVE Database V5
Not known to be exploited · CVSS 7.1 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfrappe/crmpkg:github/frappe/crmOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Monitor Frappe’s official channels for security patches addressing CVE-2025-11461 and apply them promptly once released. 2. Until patches are available, restrict external network access to Frappe CRM instances using firewalls and VPNs to limit exposure. 3. Implement Web Application Firewalls (WAFs) with SQL Injection detection and prevention rules tailored to Frappe CRM traffic patterns. 4. Conduct thorough input validation and sanitization on all user inputs, especially those interacting with SQL queries, to prevent injection vectors. 5. Review and refactor the Dashboard Controller code to replace dynamic SQL concatenation with parameterized queries or prepared statements. 6. Perform regular security audits and penetration testing focused on injection flaws in CRM applications. 7. Educate developers on secure coding practices and the risks of SQL Injection vulnerabilities. 8. Maintain comprehensive logging and monitoring to detect suspicious database query patterns indicative of exploitation attempts. 9. Consider isolating CRM databases and enforcing least privilege access controls to limit damage in case of compromise.
Description
Multiple SQL Injections in Frappe CRM Dashboard Controller due to unsafe concatenation of user-controlled parameters into dynamic SQL statements. This issue affects Frappe CRM: 1.53.1.