CVE-2019-25452
SQLi in Dolibarr Erp\/Crm 10.0.1
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2019-25452 is a high-severity SQL Injection (CWE-89) vulnerability in Dolibarr Dolibarr Erp\/Crm. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2019-25452 is an SQL injection vulnerability (CWE-89) in Dolibarr ERP/CRM version 10.0.1. The issue affects the "elemid" POST parameter in the viewcat.php endpoint, allowing unauthenticated attackers to execute arbitrary SQL queries via crafted POST requests containing malicious SQL payloads.
Unauthenticated attackers can exploit this vulnerability remotely with low complexity, requiring no privileges or user interaction. Successful exploitation enables extraction of sensitive database information using error-based or time-based blind SQL injection techniques. The CVSS v3.1 base score is 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), reflecting high confidentiality impact without affecting integrity or availability.
Advisories and references, including those from Vulncheck (https://www.vulncheck.com/advisories/dolibarr-erpcrm-sql-injection-via-elemid) and Exploit-DB (https://www.exploit-db.com/exploits/47362), provide additional details on the vulnerability, such as proof-of-concept exploits.
A proof-of-concept exploit is publicly available on Exploit-DB, indicating potential for real-world exploitation. The CVE was published on 2026-02-22.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2019-19601
Vulnerability Data
Dolibarr ERP/CRM 10.0.1 contains an SQL injection vulnerability in the elemid POST parameter of the viewcat.php endpoint that allows unauthenticated attackers to execute arbitrary SQL queries. Attackers can submit crafted POST requests with malicious SQL payloads in the elemid parameter…
more
to extract sensitive database information using error-based or time-based blind SQL injection techniques.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
SQL injection in public-facing Dolibarr web app (viewcat.php) directly enables remote unauthenticated exploitation (T1190) and extraction of sensitive data from the backend database (T1213.006).
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly mitigates SQL injection in the elemid POST parameter by requiring validation of all application inputs to block malicious SQL payloads.
Addresses the root cause by requiring timely remediation of the known flaw in Dolibarr ERP/CRM 10.0.1's viewcat.php endpoint through patching.
Mitigates error-based SQL injection techniques by suppressing detailed database error messages that could reveal sensitive information.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly target injection flaws during coding and review so largely prevent CWE-89 introduction, yet the single broad outcome leaves residual risk from incomplete neutralization techniques or missed edge cases.
Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
The same secure-coding and static-analysis activities surface missing neutralization of SQL metacharacters before the system is accepted.
Early warnings and shared best-practice information help organizations apply the latest remediation techniques against SQL-injection vulnerabilities.
Threat-intelligence feeds that surface new SQL-injection campaigns enable rapid updates to query-construction defenses and detection signatures before exploitation occurs.
Secure-coding rules and security testing phases mandate the use of parameterized queries or equivalent escaping, preventing the construction of dynamic SQL statements from untrusted input.
Language-specific secure coding rules, peer review and SAST together prevent the construction of SQL statements from untrusted data without proper parameterization or escaping.