# CVE-2021-25956: Improper User Access Control in "Dolibarr" Leads to Account Takeover

> Admins can overwrite victim passwords by renaming users to existing logins, enabling complete account takeover in Dolibarr.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Aug 2021
- **Updated:** 16 Sep 2024
- **Also known as:** BIT-dolibarr-2021-25956, GHSA-fjqg-w8g6-hhq8, UBUNTU-CVE-2021-25956

## What is CVE-2021-25956?

CVE-2021-25956 is a medium-severity missing authorization vulnerability in Dolibarr Dolibarr Erp\/Crm, published on 17 Aug 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In “Dolibarr” application, v3.3.beta1_20121221 to v13.0.2 have “Modify” access for admin level users to change other user’s details but fails to validate already existing “Login” name, while renaming the user “Login”. This leads to complete account takeover of the victim user. This happens since the password gets overwritten for the victim user having a similar login name.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2021-25956?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dolibarr/dolibarr` | Packagist | From 3.3.beta1 | 14.0.0 |
| `dolibarr/dolibarr` | Packagist | From 3.3.beta1 | 14.0.0 |
| `dolibarr` | Bitnami | From 3.3.0-beta1 to 3.3.0-beta1 | None |

Products: Dolibarr Dolibarr, Dolibarr Dolibarr Erp\/Crm.

## How do I fix CVE-2021-25956?

Upgrade dolibarr/dolibarr to 14.0.0 or later.

## Is CVE-2021-25956 being exploited?

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

## Other vulnerabilities in Dolibarr Dolibarr Erp\/Crm

- [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-2021-25956 and fix it if it is affected.

What it is: CVE-2021-25956 is a medium-severity missing authorization vulnerability in Dolibarr Dolibarr Erp\/Crm, published on 17 Aug 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-25956 in the wild and no public exploit code.

Affected packages and fixed versions:
- dolibarr/dolibarr (Packagist): affected from 3.3.beta1; fixed in 14.0.0
- dolibarr/dolibarr (Packagist): affected from 3.3.beta1; fixed in 14.0.0
- dolibarr (Bitnami): affected from 3.3.0-beta1 up to 3.3.0-beta1; 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-2021-25956/ (Markdown: https://insights.sbomify.com/CVE-2021-25956/index.md)
```

## Sources

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

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