CVE-2012-10059: Dolibarr ERP/CRM Post-Auth OS Command Injection
Dolibarr ERP/CRM versions <= 3.1.1 and <= 3.2.0 contain a post-authenticated OS command injection vulnerability in its database backup feature. The export.php script fails to sanitize the sql_compat parameter, allowing authenticated users to inject arbitrary system commands, resulting in remote code execution on the server.
Security readout for executives and security teams
Plain-English summary
Old Dolibarr ERP/CRM installations may let a logged-in user run operating-system commands through the database backup feature. This can become full server compromise. The sources do not show CISA KEV listing or confirmed active exploitation, but public exploit references exist.
Executive priority
Prioritize remediation for any internet-facing or business-critical Dolibarr instance. The vulnerability can lead to server takeover after authentication, and public exploit material lowers the barrier for abuse against unpatched legacy systems.
Technical view
CVE-2012-10059 is a post-authenticated OS command injection in Dolibarr ERP/CRM export.php. The sql_compat parameter in database backup handling is described as insufficiently sanitized, enabling authenticated remote code execution. Sources cite versions <=3.1.1 and <=3.2.0, though affected metadata is sparse.
Likely exposure
Exposure is most likely where legacy Dolibarr ERP/CRM is still reachable over a network and authenticated users can access database backup/export functionality. Internet-facing deployments, shared accounts, weak credentials, or broad admin access increase practical risk.
Exploitation context
The bundle includes public exploit references, including Exploit-DB, Full Disclosure, and Metasploit. KEV is false, and the provided sources do not confirm active exploitation in the wild. Treat exploitability as demonstrated, not necessarily currently observed.
Researcher notes
The core issue maps to CWE-78 in the sql_compat parameter of export.php. The record is recently published for an older 2012 issue, and affected-version metadata appears limited. Do not assume unauthenticated exposure from these sources.
Mitigation direction
Inventory Dolibarr deployments and identify versions at or below the described affected ranges.
Check current Dolibarr vendor guidance for supported upgrade or migration paths.
Restrict database backup/export access to trusted administrators only.
Remove legacy Dolibarr instances from direct internet exposure where possible.
Review server logs for suspicious backup/export activity or unexpected process execution.
Validation and detection
Confirm the exact Dolibarr version and whether the instance exposes export.php.
Review role permissions for database backup and export features.
Check application and web server logs around backup/export requests.
Verify remediation against vendor guidance rather than relying only on filtering.
Assess whether any affected host shows signs of command execution or persistence.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.