How severe is CVE-2017-7886?

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

Which packages are affected by CVE-2017-7886?

CVE-2017-7886 affects the following packages: dolibarr/dolibarr (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2017-7886?

The records we use list no patched version of dolibarr/dolibarr for CVE-2017-7886. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2017-7886 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-2017-7886 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-2017-7886 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2017-7886, including 1 in-the-wild exploitation 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-2017-7886?

CVE-2017-7886 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 78th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2017-7886?

CVE-2017-7886 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-2017-7886 published, and has it been updated?

CVE-2017-7886 was published on May 10, 2017 and was last updated on October 24, 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-2017-7886 — dolibarr

CRITICAL

CVE-2017-7886 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in dolibarr/dolibarr. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Dolibarr SQL Injection in doli/theme/eldy/style.css.php via the lang parameter

Also known asGHSA-gw37-vmvw-f833

Published

May 10, 2017

Updated

Oct 24, 2026

Affected

1 pkg

Patched

See advisory

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs78th percentile — riskier than 78% 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

Dolibarr ERP/CRM 4.0.4 has SQL Injection in doli/theme/eldy/style.css.php via the lang parameter.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`dolibarr/dolibarr`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

dolibarr erp\/crmdolibarr

1 version

4.0.4

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.

Dolibarr ERP/CRM 4.0.4 has SQL Injection in doli/theme/eldy/style.css.ph…

foxmole.comNVDMay 2017

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.
Remediation status
The records we use list no patched version of dolibarr/dolibarr for CVE-2017-7886. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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

Dolibarr ERP/CRM 4.0.4 has SQL Injection in doli/theme/eldy/style.css.php via the lang parameter.

O3 Security · Impact-Aware SCA

Is CVE-2017-7886 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. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

dolibarr

5.8/10

Maintained10/10

Code-Review4/10

Branch-Protection3/10

Assessed Nov 2, 2026

Timeline

Disclosed

May 10, 2017

First exploit

May 15, 2017

5 days after disclosure — rapid exploitation

Last updated

Oct 24, 2026

Identifiers

CVE-2017-7886

GHSA-gw37-vmvw-f833

References

Advisorynvd.nist.gov · CVE 2017 7886 Packagegithub.com · dolibarr Evidencefoxmole.com · foxmole 2017 02 23.txt

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 24, 2026

CVE-2017-7886 — 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

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2017-7886 in your dependencies?