# CVE-2018-25357: Dolibarr ERP CRM 7.0.3 Remote Code Execution via install/step1.php

> Unauthenticated attackers can execute arbitrary code by injecting PHP into the installer's database name parameter, requiring the installation interface to be accessible.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 May 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-hxmh-2xc4-c894, UBUNTU-CVE-2018-25357, USN-8448-1

## What is CVE-2018-25357?

CVE-2018-25357 is a critical code injection vulnerability in Dolibarr Dolibarr Erp\/Crm, published on 23 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dolibarr ERP CRM 7.0.3 contains a remote code execution vulnerability that allows unauthenticated attackers to execute arbitrary code by injecting PHP code through the db_name parameter. Attackers can send a POST request to install/step1.php with malicious PHP code in the db_name parameter, then execute commands via the check.php endpoint using the cmd GET parameter.

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

## Which versions are affected by CVE-2018-25357?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dolibarr/dolibarr` | Packagist | All versions | 6.0.8 |
| `dolibarr/dolibarr` | Packagist | All versions | 6.0.8 |
| `dolibarr/dolibarr` | Packagist | From 7.0.0 | 7.0.4 |
| `dolibarr/dolibarr` | Packagist | From 7.0.0 | 7.0.4 |

Products: Dolibarr Dolibarr Erp\/Crm.

## How do I fix CVE-2018-25357?

Upgrade dolibarr/dolibarr to a fixed version for your release line: 6.0.8 or 7.0.4.

## Is CVE-2018-25357 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25357 exists.

## 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-2022-40871](https://insights.sbomify.com/CVE-2022-40871/): Dolibarr vulnerable to Eval Injection (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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25357 and fix it if it is affected.

What it is: CVE-2018-25357 is a critical code injection vulnerability in Dolibarr Dolibarr Erp\/Crm, published on 23 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25357 exists.

Affected packages and fixed versions:
- dolibarr/dolibarr (Packagist): affected all versions; fixed in 6.0.8
- dolibarr/dolibarr (Packagist): affected all versions; fixed in 6.0.8
- dolibarr/dolibarr (Packagist): affected from 7.0.0; fixed in 7.0.4
- dolibarr/dolibarr (Packagist): affected from 7.0.0; fixed in 7.0.4

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-2018-25357/ (Markdown: https://insights.sbomify.com/CVE-2018-25357/index.md)
```

## Sources

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

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