# CVE-2022-40871: Dolibarr vulnerable to Eval Injection

> Attackers can execute arbitrary code by injecting malicious payloads into the database via the default administrator installation page.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2022
- **Updated:** 15 May 2025
- **Also known as:** BIT-dolibarr-2022-40871, GHSA-7cm4-vmf2-8wf2, UBUNTU-CVE-2022-40871

## What is CVE-2022-40871?

CVE-2022-40871 is a critical code injection vulnerability in Dolibarr Dolibarr Erp\/Crm, published on 12 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dolibarr ERP & CRM <=15.0.3 is vulnerable to Eval injection. By default, any administrator can be added to the installation page of dolibarr, and if successfully added, malicious code can be inserted into the database and then execute it by eval.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2022-40871?

3 open source packages ship an affected version, including dolibarr/dolibarr and dolibarr. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dolibarr/dolibarr` | Packagist | All versions to 15.0.3 | None |
| `dolibarr/dolibarr` | Packagist | All versions to 15.0.3 | None |
| `dolibarr` | Bitnami | All versions to 15.0.3 | None |

Products: Dolibarr Dolibarr Erp\/Crm.

## How do I fix CVE-2022-40871?

No fix has been published for CVE-2022-40871 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-40871 being exploited?

There is no known exploitation of CVE-2022-40871 in the wild and no public exploit code.

## Other vulnerabilities in Dolibarr Dolibarr Erp\/Crm

- [CVE-2022-43138](https://insights.sbomify.com/CVE-2022-43138/): Dolibarr vulnerable to privilege escalation (critical 9.8)
- [CVE-2021-33816](https://insights.sbomify.com/CVE-2021-33816/): Dolibarr remote PHP code execution (critical 9.8)
- [CVE-2020-7995](https://insights.sbomify.com/CVE-2020-7995/): Dolibarr Improper Restriction of Excessive Authentication Attempts (critical 9.8)
- [CVE-2013-2091](https://insights.sbomify.com/CVE-2013-2091/): SQL injection in dolibarr (critical 9.8)
- [CVE-2013-2093](https://insights.sbomify.com/CVE-2013-2093/): Command injection in dolibarr (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40871 and fix it if it is affected.

What it is: CVE-2022-40871 is a critical code injection vulnerability in Dolibarr Dolibarr Erp\/Crm, published on 12 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-40871 in the wild and no public exploit code.

Affected packages and fixed versions:
- dolibarr/dolibarr (Packagist): affected all versions up to 15.0.3; no fix listed
- dolibarr/dolibarr (Packagist): affected all versions up to 15.0.3; no fix listed
- dolibarr (Bitnami): affected all versions up to 15.0.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-40871/ (Markdown: https://insights.sbomify.com/CVE-2022-40871/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-40871
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-40871
- OSV: https://osv.dev/vulnerability/CVE-2022-40871

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-40871/
Summaries are generated and may contain mistakes; the official description above is the record.