# CVE-2020-14209: Dolibarr Unrestricted Upload of File with Dangerous Type

> Low-privilege users can upload dangerous file types or .htaccess files to execute arbitrary code on Dolibarr instances.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 2 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2gcp-xwxg-hqg3, UBUNTU-CVE-2020-14209

## What is CVE-2020-14209?

CVE-2020-14209 is a high-severity vulnerability in n/a, published on 2 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Dolibarr before 11.0.5 allows low-privilege users to upload files of dangerous types, leading to arbitrary code execution. This occurs because .pht and .phar files can be uploaded. Also, a .htaccess file can be uploaded to reconfigure access control (e.g., to let .noexe files be executed as PHP code to defeat the .noexe protection mechanism).

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2020-14209?

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 | 11.0.5 |
| `dolibarr/dolibarr` | Packagist | All versions | 11.0.5 |

Products: Dolibarr Dolibarr.

## How do I fix CVE-2020-14209?

Upgrade dolibarr/dolibarr to 11.0.5 or later.

## Is CVE-2020-14209 being exploited?

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

Public exploit code:

- Dolibarr ERP 11.0.4 - File Upload Restrictions Bypass (Authenticated RCE) (exploitdb)

## 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-2020-14209 and fix it if it is affected.

What it is: CVE-2020-14209 is a high-severity vulnerability in n/a, published on 2 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14209 in the wild and no public exploit code.

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

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

## Sources

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

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