# CVE-2018-10092: Dolibarr arbitrary commands execution

> Remote attackers can execute arbitrary commands via the admin panel's antivirus configuration in Dolibarr.

- **Severity:** High 8.0 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6j62-m2vv-wc3m, UBUNTU-CVE-2018-10092

## What is CVE-2018-10092?

CVE-2018-10092 is a high-severity command injection vulnerability in n/a, published on 22 May 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The admin panel in Dolibarr before 7.0.2 might allow remote attackers to execute arbitrary commands by leveraging support for updating the antivirus command and parameters used to scan file uploads.

Weakness: CWE-862 (Missing Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dolibarr/dolibarr` | Packagist | All versions | 7.0.2 |
| `dolibarr/dolibarr` | Packagist | All versions | 7.0.2 |

Products: Dolibarr Dolibarr.

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

Upgrade dolibarr/dolibarr to 7.0.2 or later.

## Is CVE-2018-10092 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-19212](https://insights.sbomify.com/CVE-2019-19212/): Dolibarr Cross-site Scripting via the qty parameter in product/fournisseurs.php (critical 9.8)
- [CVE-2018-16809](https://insights.sbomify.com/CVE-2018-16809/): Dolibarr SQL injection via the integer parameters qty and value_unit (critical 9.8)
- [CVE-2018-10094](https://insights.sbomify.com/CVE-2018-10094/): Dolibarr SQL injection vulnerability (critical 9.8)
- [CVE-2018-9019](https://insights.sbomify.com/CVE-2018-9019/): Dolibarr SQL Injection vulnerability (critical 9.8)
- [CVE-2017-14238](https://insights.sbomify.com/CVE-2017-14238/): Dolibarr SQL injection vulnerability in admin/menus/edit.php (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-10092 is a high-severity command injection vulnerability in n/a, published on 22 May 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-10092 in the wild and no public exploit code.

Affected packages and fixed versions:
- dolibarr/dolibarr (Packagist): affected all versions; fixed in 7.0.2
- dolibarr/dolibarr (Packagist): affected all versions; fixed in 7.0.2

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

## Sources

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

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