# CVE-2026-71505: Dolibarr < 24.0.0 REST API Broken Object-Level Authorization via Third-Party Write Route

> Authenticated attackers can overwrite WebPortal passwords for any company via the REST API, gaining unauthorized access to invoice data and previous credentials.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-c275-q2j8-wwg9

## What is CVE-2026-71505?

CVE-2026-71505 is a high-severity missing authorization vulnerability in dolibarr, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Dolibarr before 24.0.0 contains a broken object-level authorization vulnerability in the REST API third-party site account write routes that allows authenticated attackers with third-party creation rights to overwrite the WebPortal password of any company by bypassing per-object access checks that are only enforced on read routes. Attackers can replace the victim company's WebPortal password through the write endpoint, authenticate as that company to access its invoice data, and also obtain the victim's previous password verifier from the API response.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-71505?


## How do I fix CVE-2026-71505?

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

## Is CVE-2026-71505 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71505 and fix it if it is affected.

What it is: CVE-2026-71505 is a high-severity missing authorization vulnerability in dolibarr, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-71505 exists.

Affected product: dolibarr. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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