CVE-2025-70981
SQL Injection in CordysCRM 1.4.1 Employee List Interface
Publication date: 2026-02-12
Last updated on: 2026-02-18
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| fit2cloud | cordys_crm | 1.4.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-70981 is a SQL Injection vulnerability found in CordysCRM version 1.4.1. It occurs in the employee list query interface, specifically through the departmentIds parameter in the /user/list endpoint. This means that an attacker can manipulate the SQL query by injecting malicious SQL code via this parameter.
How can this vulnerability impact me? :
This SQL Injection vulnerability can allow an attacker to execute arbitrary SQL commands on the database used by CordysCRM. This could lead to unauthorized access to sensitive employee data, data modification, or even deletion. It may also enable attackers to escalate privileges or compromise the entire system depending on the database permissions.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'The vulnerability in CordysCRM 1.4.1 is an SQL Injection in the /user/list interface via the departmentIds parameter. Detection can involve sending crafted requests to this endpoint to test for SQL injection.'}, {'type': 'paragraph', 'content': 'A common approach is to use tools like curl or sqlmap to test the parameter. For example, using curl to send a request with a typical SQL injection payload:'}, {'type': 'list_item', 'content': 'curl -v "http://<target>/user/list?departmentIds=1\' OR \'1\'=\'1"'}, {'type': 'paragraph', 'content': 'Alternatively, sqlmap can be used to automate detection:'}, {'type': 'list_item', 'content': 'sqlmap -u "http://<target>/user/list?departmentIds=1" --batch'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Restrict access to the /user/list endpoint to trusted users or networks.
- Apply input validation and sanitization on the departmentIds parameter to prevent injection.
- If possible, update or patch CordysCRM to a version that addresses this vulnerability.
- Use web application firewalls (WAF) to detect and block SQL injection attempts targeting this endpoint.