Skip to content
Fencer Intel
critical 9.8

CVE-2018-10094 in the critical feed json

Dolibarr SQL injection vulnerability

published 8y ago modified 4mo ago also GHSA-57wj-22w9-wm9r , EUVD-2022-2525

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
69.3%
EPSS 69.3% chance of exploitation in 30 days, percentile 99.3%
public exploits
2
Metasploit and Exploit-DB

Summary

SQL injection vulnerability in Dolibarr before 7.0.2 allows remote attackers to execute arbitrary SQL commands via vectors involving integer parameters without quotes.

Patch / fix

  • packagist dolibarr/dolibarr 7.0.2
  • dolibarr dolibarr 7.0.2

Is CVE-2018-10094 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (Metasploit auxiliary/gather/dolibarr_creds_sqli)

Exploit prediction

69.34% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit auxiliary/gather/dolibarr_creds_sqli Dolibarr Gather Credentials via SQL Injection metasploit auxiliary, normal rank, 2018-05-30
  • EDB-44805 Dolibarr ERP/CRM 7.0.0 - (Authenticated) SQL Injection webapps, 2018-05-30
  • sysdream.com https://sysdream.com/news/lab/2018-05-21-cve-2018-10094-dolibarr-sql-injection-vulnerability/ referenced PoC, tagged "exploit" by a source, unverified
  • openwall.com http://www.openwall.com/lists/oss-security/2018/05/21/1 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist dolibarr/dolibarr
<7.0.2
7.0.2

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.