VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

dolibarr/dolibarr: vulnerability history, versions and safety

dolibarr/dolibarr is a package in the Packagist ecosystem. Vulert records 127 vulnerabilities for it across 115 releases, from Nov 2019 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
127 vulnerabilities recorded C28 H38 M56 L5
i
50 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
9 in the last 12 months

Most recent disclosure 01 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all dolibarr/dolibarr vulnerabilities

Vulert verdict on dolibarr/dolibarr i

Updated on 23 Oct 2026

Careful: 50 of the 127 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 127 vulnerabilities on record across 6 years, 9 in the last year.

What to do: Plan around the 50 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 127 over 6 years · 9 in the last year i
  • Latest disclosure 01 Jun 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 50 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for dolibarr/dolibarr, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
21.0.0-beta L2 No Details →
18.0.4 H1 No Details →
15.0.3 C3 H11 M9 L3 No Details →
15.0.2 C3 H11 M9 L3 No Details →
15.0.1 C3 H11 M9 L3 No Details →
15.0.0 C3 H12 M9 L3 No Details →
14.0.5 C3 H13 M12 L3 No Details →
14.0.4 C3 H13 M12 L3 No Details →
14.0.3 C3 H13 M12 L3 No Details →
14.0.2 C3 H13 M13 L3 No Details →
14.0.1 C3 H13 M13 L3 No Details →
14.0.0 C4 H14 M13 L3 No Details →
13.0.5 C6 H17 M14 L3 No Details →
13.0.4 C6 H17 M14 L3 No Details →
13.0.3 C6 H17 M14 L3 No Details →
13.0.2 C6 H17 M15 L3 No Details →
13.0.1 C5 H17 M15 L3 No Details →
13.0.0 C5 H17 M15 L3 No Details →
12.0.5 C5 H17 M17 L3 No Details →
12.0.4 C5 H17 M16 L3 No Details →
12.0.3 C5 H18 M16 L3 No Details →
12.0.2 C5 H18 M16 L3 No Details →
12.0.1 C5 H18 M16 L3 No Details →
12.0.0 C5 H18 M16 L3 No Details →
11.0.5 C5 H19 M16 L3 No Details →
11.0.4 C5 H21 M21 L3 No Details →
11.0.3 C5 H21 M20 L3 No Details →
11.0.2 C5 H21 M20 L3 No Details →
11.0.1 C5 H21 M20 L3 No Details →
11.0.0 C5 H21 M22 L3 No Details →
10.0.7 C5 H21 M22 L3 No Details →
10.0.6 C6 H22 M25 L3 No Details →
10.0.5 C5 H22 M23 L3 No Details →
10.0.4 C5 H22 M23 L3 No Details →
10.0.3 C6 H22 M24 L3 No Details →
10.0.2 C6 H23 M29 L3 No Details →
10.0.1 C6 H24 M27 L3 No Details →
10.0.0 C6 H24 M27 L3 No Details →
9.0.5 M4 No Details →
9.0.4 C6 H23 M27 L3 No Details →
9.0.3 C6 H23 M27 L3 No Details →
9.0.2 C6 H25 M27 L3 No Details →
9.0.1 C8 H25 M27 L3 No Details →
9.0.0 C8 H25 M27 L3 No Details →
8.0.6 C8 H25 M27 L3 No Details →
8.0.5 C8 H25 M27 L3 No Details →
8.0.4 C8 H26 M27 L3 No Details →
8.0.3 C8 H28 M31 L3 No Details →
8.0.2 C8 H28 M31 L3 No Details →
8.0.1 C8 H28 M31 L3 No Details →
8.0.0 C8 H28 M31 L3 No Details →
7.0.5 C8 H28 M31 L3 No Details →
7.0.4 C8 H28 M31 L3 No Details →
7.0.3 C13 H28 M31 L3 No Details →
7.0.2 C9 H28 M31 L3 No Details →
7.0.1 C11 H29 M32 L3 No Details →
7.0.0 C12 H31 M34 L3 No Details →
6.0.8 C11 H30 M35 L3 No Details →
6.0.7 C11 H30 M35 L3 No Details →
6.0.6 C11 H30 M35 L3 No Details →
6.0.5 C11 H30 M35 L3 No Details →
6.0.4 C14 H31 M37 L3 No Details →
6.0.3 C14 H31 M36 L3 No Details →
6.0.2 C14 H31 M36 L3 No Details →
6.0.1 C14 H31 M36 L3 No Details →
6.0.0 C16 H32 M38 L3 No Details →
6.0.0-rc C16 H32 M37 L3 No Details →
6.0.0-beta C16 H32 M37 L3 No Details →
5.0.7 C16 H32 M37 L3 No Details →
5.0.6 C16 H32 M37 L3 No Details →
5.0.5 C16 H32 M37 L3 No Details →
5.0.4 C16 H32 M37 L3 No Details →
5.0.3 C16 H34 M38 L3 No Details →
5.0.2 C17 H34 M38 L3 No Details →
5.0.1 C17 H34 M38 L3 No Details →
5.0.0 C17 H34 M38 L3 No Details →
5.0.0-rc2 C17 H34 M38 L3 No Details →
5.0.0-rc1 C17 H34 M38 L3 No Details →
5.0.0-beta C17 H34 M38 L3 No Details →
4.0.6 C17 H34 M38 L3 No Details →
4.0.5 C17 H34 M38 L3 No Details →
4.0.4 C19 H34 M40 L3 No Details →
4.0.3 C18 H34 M39 L3 No Details →
4.0.2 C18 H34 M39 L3 No Details →
4.0.1 C18 H34 M39 L3 No Details →
4.0.0 C18 H34 M39 L3 No Details →
4.0.0-rc2 C18 H34 M39 L3 No Details →
4.0.0-rc C18 H34 M39 L3 No Details →
4.0.0-beta C18 H34 M39 L3 No Details →
3.9.4 C18 H34 M39 L3 No Details →
3.9.3 C18 H34 M39 L3 No Details →
3.9.2 C18 H34 M39 L3 No Details →
3.9.1 C18 H34 M39 L3 No Details →
3.9.0 C18 H34 M39 L3 No Details →
3.9.0-rc2 C18 H34 M39 L3 No Details →
3.9.0-rc C18 H34 M39 L3 No Details →
3.8.4 C18 H34 M39 L3 No Details →
3.8.3 C18 H34 M40 L3 No Details →
3.8.2 C18 H34 M40 L3 No Details →
3.8.1 C18 H34 M40 L3 No Details →
3.8.0 C18 H34 M40 L3 No Details →
3.8.0-beta C18 H34 M40 L3 No Details →
3.7.4 C17 H34 M40 L3 No Details →
3.7.3 C17 H34 M40 L3 No Details →
3.7.2 C17 H34 M40 L3 No Details →
3.7.1 C17 H34 M40 L3 No Details →
3.7.0 C17 H34 M40 L3 No Details →
3.6.6 C17 H34 M40 L3 No Details →
3.6.5 C17 H34 M40 L3 No Details →
3.6.4 C17 H34 M40 L3 No Details →
3.6.3 C17 H34 M40 L3 No Details →
3.6.2 C17 H34 M40 L3 No Details →
3.6.1 C17 H34 M40 L3 No Details →
3.6.0 C17 H34 M40 L3 No Details →
3.6.0-beta C17 H34 M40 L3 No Details →

Newest 115 of 115 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2020 2
  • 2021 5
  • 2022 88
  • 2023 9
  • 2024 9
  • 2025 4
  • 2026 9

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 9 of the 127 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for dolibarr/dolibarr

The 5 most severe of 127 vulnerabilities recorded for this package

Search all 127 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-33816: Dolibarr remote PHP code execution 9.8 critical 14.0.0 24 May 2022
CVE-2022-40931: Cross Site Scripting (XSS) in dutchcoders Transfer.sh 9.8 critical 16.0.3 21 Nov 2022
CVE-2018-16809: Dolibarr SQL injection via the integer parameters qty and value_unit 9.8 critical No fix published 14 May 2022
CVE-2022-43138: Dolibarr Open Source ERP & CRM Privilege Escalation 9.8 critical 14.0.1 17 Nov 2022
CVE-2017-7888: Dolibarr ERP and CRM Insecure Encryption 9.8 critical No fix published 17 May 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About dolibarr/dolibarr

Is dolibarr/dolibarr safe to use?

Vulert records 127 vulnerabilities for dolibarr/dolibarr in Packagist: 28 critical, 38 high, 56 medium and 5 low. 50 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does dolibarr/dolibarr have?

127 vulnerabilities are recorded for dolibarr/dolibarr in the Packagist ecosystem: 28 critical, 38 high, 56 medium and 5 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new dolibarr/dolibarr vulnerabilities disclosed?

9 vulnerabilities were recorded for dolibarr/dolibarr in the last 12 months, and the oldest entry in this database dates to 08 Nov 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of dolibarr/dolibarr are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor dolibarr/dolibarr for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the dolibarr/dolibarr version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.