# CVE-2026-71511: Dolibarr < 24.0.0 Members REST API Sensitive Data Exposure via Member Endpoints

> Authenticated attackers with member-read rights can retrieve bcrypt password verifiers via REST API endpoints, enabling offline password cracking.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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-589q-6598-2vqx

## What is CVE-2026-71511?

CVE-2026-71511 is a high-severity 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 sensitive data exposure vulnerability in the Members REST API that allows authenticated attackers with member-read rights to retrieve bcrypt password verifiers by querying member endpoints. Attackers can call the individual member or member list endpoints to obtain crypted password verifier fields that are not filtered by the base API serializer or the Members API class, potentially enabling offline password cracking attacks.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-71511 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71511 is a high-severity 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-71511 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-71511/ (Markdown: https://insights.sbomify.com/CVE-2026-71511/index.md)
```

## Sources

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

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