CVE-2025-70981: CordysCRM · SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Feb 2026
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 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2025-70981, organizations should immediately restrict external access to the /user/list endpoint, especially the departmentIds parameter, using network segmentation and access control lists. Deploying a web application firewall (WAF) with robust SQL Injection detection and prevention rules can help block exploitation attempts. Conduct thorough input validation and sanitization on all user-supplied parameters, particularly departmentIds, to prevent injection. Monitor database logs and application logs for unusual query patterns indicative of SQL Injection attempts. If possible, disable or limit the use of the vulnerable interface until a vendor patch or update is available. Engage with the CordysCRM vendor or community for updates or unofficial patches. Additionally, implement least privilege principles on database accounts used by the CRM to minimize damage in case of exploitation. Regularly back up CRM data and test restoration procedures to ensure resilience against data corruption or deletion.
Description
CordysCRM 1.4.1 is vulnerable to SQL Injection in the employee list query interface (/user/list) via the departmentIds parameter.