How severe is CVE-2018-10094?

CVE-2018-10094 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-10094?

CVE-2018-10094 affects the following packages: dolibarr/dolibarr (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2018-10094?

Update dolibarr/dolibarr to 7.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-10094 is resolved across your whole dependency graph.

How do I detect CVE-2018-10094 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dolibarr/dolibarr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-10094 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2018-10094 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2018-10094, including 1 documented proof-of-concept exploit on Exploit-DB and 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-10094?

CVE-2018-10094 has an EPSS (Exploit Prediction Scoring System) score of 69.3%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2018-10094?

CVE-2018-10094 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2018-10094 published, and has it been updated?

CVE-2018-10094 was published on May 22, 2018 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

CVE-2018-10094 — dolibarr

CRITICALFix: Dolibarr/dolibarr@7ade4e3

CVE-2018-10094 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in dolibarr/dolibarr. 5 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for dolibarr/dolibarr — see the affected versions and patch details below.

Dolibarr SQL injection vulnerability

Also known asGHSA-57wj-22w9-wm9r

Published

May 22, 2018

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

5 known

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

69.3%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘dolibarr/dolibarr

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`dolibarr/dolibarr`	all versions	7.0.2`composer require dolibarr/dolibarr:^7.0.2`

Affected Products

1 product · 1 configurations

Application

dolibarrdolibarr

< 7.0.2

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-44805webappsphp✓ Verified

Dolibarr ERP/CRM 7.0.0 - (Authenticated) SQL Injection

by Sysdream · May 30, 2018

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dolibarr/dolibarr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dolibarr/dolibarr to 7.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-10094 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2018-10094 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-89SQL Injection

Weaponization

No Nuclei template or Metasploit module yet. 5 public proof-of-concept references are listed on this page.

OpenSSF Scorecard

Package health score

dolibarr

6.1/10

Maintained10/10

Code-Review2/10

Branch-Protection3/10

Assessed Nov 9, 2026

Timeline

Disclosed

May 22, 2018

First exploit

May 30, 2018

7 days after disclosure — rapid exploitation

Last updated

Oct 20, 2026

Identifiers

CVE-2018-10094

GHSA-57wj-22w9-wm9r

References

Advisorygithub.com · ChangeLog Advisorynvd.nist.gov · CVE 2018 10094 Fixgithub.com · 7ade4e37f24d6859987bb9f6232f604325633fdd Websysdream.com · 2018 05 21 cve 2018 10094 dolibarr sql injection vulnerability Webexploit-db.com Packagegithub.com · dolibarr Evidenceopenwall.com Evidencesysdream.com · 2018 05 21 cve 2018 10094 dolibarr sql injection vulnerability Evidenceexploit-db.com

Related vulnerabilities

This CVE is critical severity; 2 of 8 other CVEs affecting dolibarr/dolibarr are rated as high or higher (top: critical).

CVE-2026-33944CVE-2026-10215CVE-2018-25357CVE-2026-7689CVE-2026-7688CVE-2026-31018CVE-2026-31019CVE-2026-23500

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2018-10094 — dolibarr

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2018-10094 in your dependencies?