Quick answers
- Is CVE-2026-71511 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-71511 being exploited in the wild.
- How severe is CVE-2026-71511?
- Medium severity, with a CVSS score of 6.5, published 24 August 2026.
- Which products and versions are affected?
- Dolibarr before 24.0.0.
- Is there a fix for CVE-2026-71511?
- A patch was published on 2026: Fixed in version 24.0.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-71511 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-71511?
- Check whether you run Dolibarr at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a sensitive data exposure flaw in the Members REST API. The root cause is improper filtering in the base API serializer and Members API class, which fails to remove the "pass_indatabase_crypted" field from API responses. An authenticated attacker with member-read rights can call member list or individual member endpoints to retrieve bcrypt password verifiers that should not be exposed. This enables offline brute-force or dictionary attacks against member credentials. The fix is patched in Dolibarr 24.0.0 and later, which removes the crypted password field from API serialization.
Affected products
- Dolibarr Dolibarr before 24.0.0
Timeline
- 2026-08-24: disclosed
- 2026: patched: Fixed in version 24.0.0