CVE-2026-71511

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
The EG Score, 6.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 24, 2026

Last Modified

October 12, 2026

Advisory Details (4)

Auto-updated Aug 24, 2026
Patch available. Sources: github_release, github_commit.
Web page

Dolibarr < 24.0.0 Members REST API Sensitive Data Exposure via Member Endpoints | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dolibarr-members-rest-api-sensitive-data-exposure-via-member-endpoints
GitHub commit Patch Available

commit b1691356eb96 (Dolibarr/dolibarr)

Patch available: Dolibarr/dolibarr 24.0.0 (contains commit b1691356eb96)

https://github.com/Dolibarr/dolibarr/commit/b1691356eb96d962833e5c7325c9e58e6823c78d
GitHub release Patch Available

24.0.0

Patch available: Dolibarr/dolibarr 24.0.0

https://github.com/Dolibarr/dolibarr/releases/tag/24.0.0
Web page

CVE-2026-71511: Dolibarr Members API Exposes Password Hashes

https://codeant.ai/security-research/cve-2026-71511-dolibarr-members-api-exposes-password-hashes

Vendor Advisories for CVE-2026-71511(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 75× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 131 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 31 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-10-12 21:27 UTCEG score recompute
  3. 2026-10-12 21:27 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-10-12 15:42 UTCEG score recompute
  6. 2026-10-11 19:28 UTCEG score recompute
  7. 2026-10-11 16:43 UTCEG score recompute
  8. 2026-10-11 14:03 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-10-10 12:31 UTCEG score recompute
  12. 2026-10-10 12:31 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-10-09 07:56 UTCEG score recompute
  15. 2026-10-09 07:56 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  16. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-10-08 06:10 UTCEG score recompute
  18. 2026-10-08 06:10 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  20. 2026-10-07 04:28 UTCEG score recompute
  21. 2026-10-07 04:28 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  22. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-10-06 02:47 UTCEG score recompute
  24. 2026-10-06 02:47 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  25. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 75 more
  1. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-04 21:17 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  3. 2026-10-03 19:23 UTCEG score recompute
  4. 2026-10-03 19:23 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  5. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-02 17:09 UTCEG score recompute
  7. 2026-10-02 17:08 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  8. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-01 15:28 UTCEG score recompute
  10. 2026-10-01 15:28 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  11. 2026-10-01 08:41 UTCEG score recompute
  12. 2026-10-01 08:41 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  13. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-09-30 06:59 UTCEG score recompute
  15. 2026-09-30 06:59 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  16. 2026-09-29 01:41 UTCEG score recompute
  17. 2026-09-29 01:41 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  18. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-09-28 00:00 UTCEG score recompute
  20. 2026-09-28 00:00 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  21. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-09-26 22:19 UTCEG score recompute
  23. 2026-09-26 22:18 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-09-25 01:09 UTCEG score recompute
  26. 2026-09-25 01:09 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  27. 2026-09-23 23:27 UTCEG score recompute
  28. 2026-09-23 23:27 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  29. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  30. 2026-09-22 21:34 UTCEG score recompute
  31. 2026-09-22 21:34 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  32. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  33. 2026-09-21 19:53 UTCEG score recompute
  34. 2026-09-21 19:53 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  35. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  36. 2026-09-20 18:12 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  37. 2026-09-19 16:30 UTCEG score recompute
  38. 2026-09-19 16:30 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  39. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  40. 2026-09-18 14:49 UTCEG score recompute
  41. 2026-09-18 14:49 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  42. 2026-09-17 13:08 UTCEG score recompute
  43. 2026-09-17 13:08 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  44. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  45. 2026-09-16 10:45 UTCEG score recompute
  46. 2026-09-16 10:45 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  47. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  48. 2026-09-15 08:56 UTCEG score recompute
  49. 2026-09-15 08:56 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  50. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  51. 2026-09-14 07:15 UTCEG score recompute
  52. 2026-09-14 07:15 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  53. 2026-09-13 05:34 UTCEG score recompute
  54. 2026-09-13 05:34 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  55. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  56. 2026-09-12 03:53 UTCEG score recompute
  57. 2026-09-12 03:53 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  58. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  59. 2026-09-11 02:12 UTCEG score recompute
  60. 2026-09-11 02:12 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  61. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  62. 2026-09-10 00:31 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  63. 2026-09-08 20:52 UTCEG score recompute
  64. 2026-09-08 20:52 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  65. 2026-09-08 06:13 UTCEG score recompute
  66. 2026-09-08 06:13 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  67. 2026-09-07 04:30 UTCEG score recompute
  68. 2026-09-07 04:30 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  69. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  70. 2026-09-06 02:39 UTCEG score recompute
  71. 2026-09-06 02:39 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  72. 2026-09-05 00:58 UTCEG score recompute
  73. 2026-09-05 00:58 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5
  74. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  75. 2026-09-03 23:14 UTCGHSA enrichmentGHSA-589q-6598-2vqx · GitHub severity HIGH · GitHub CVSS 6.5

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71511?
CVE-2026-71511 is a medium-severity vulnerability; its CVE record was published on August 24, 2026. 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…
When was CVE-2026-71511 made public?
CVE-2026-71511 was made public on August 9, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 24, 2026. EchelonGraph's copy of the record carries a last-modified date of October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-71511 actively exploited?
CVE-2026-71511 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71511?
CVE-2026-71511 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71511?
A fix for CVE-2026-71511 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71511 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-71511

Explore →

Is Your Infrastructure Affected by CVE-2026-71511?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs