CVE-2026-71506

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. A secondary CVSS source baseline 8.1; 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
8.1EG
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.5%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Dolibarr before 24.0.0 contains an improper authorization vulnerability in the payments REST API delete endpoint that allows authenticated attackers with invoice-deletion rights to permanently delete any payment record by bypassing the intended payment-issuance rights check. Attackers can exploit this misconfigured permission check to zero paid amounts on invoices and remove entries from accounting exports, causing financial data integrity loss.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity81% × 45%
The EG Score, 8.1 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.5%
EPSS %ILE
43rd
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_commit, github_release.
Web page

Dolibarr < 24.0.0 Payments REST API Improper Authorization via Delete Endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dolibarr-payments-rest-api-improper-authorization-via-delete-endpoint
GitHub release Patch Available

24.0.0

Patch available: Dolibarr/dolibarr 24.0.0

https://github.com/Dolibarr/dolibarr/releases/tag/24.0.0
GitHub commit Patch Available

commit e01a12ffea46 (Dolibarr/dolibarr)

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

https://github.com/Dolibarr/dolibarr/commit/e01a12ffea4675f5bcc1c886f06ec6a29d5e4801
Web page

CVE-2026-71506: Dolibarr Payment Deletion via Incorrect Authorization

https://codeant.ai/security-research/cve-2026-71506-dolibarr-payment-deletion-via-incorrect-authorization

Vendor Advisories for CVE-2026-71506(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 / 100× 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 181 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 81 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.5% · 43rd percentile
  2. 2026-10-12 22:26 UTCEG score recompute
  3. 2026-10-12 22:26 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd 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.5% · 43rd percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-10-10 12:31 UTCEG score recompute
  12. 2026-10-10 12:31 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-09 04:42 UTCEG score recompute
  15. 2026-10-09 04:42 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  16. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-08 03:50 UTCEG score recompute
  18. 2026-10-08 03:50 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-10-07 04:22 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  21. 2026-10-06 16:10 UTCEG score recompute
  22. 2026-10-06 16:10 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-06 02:47 UTCEG score recompute
  25. 2026-10-06 02:47 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
Show 75 more
  1. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-10-05 09:21 UTCEG score recompute
  3. 2026-10-05 09:21 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-10-04 20:41 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  6. 2026-10-04 04:54 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  7. 2026-10-03 16:30 UTCEG score recompute
  8. 2026-10-03 16:30 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  9. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-10-03 04:08 UTCEG score recompute
  11. 2026-10-03 04:08 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-10-02 15:51 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-10-02 03:40 UTCEG score recompute
  14. 2026-10-02 03:40 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  15. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-01 15:28 UTCEG score recompute
  17. 2026-10-01 15:28 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  18. 2026-10-01 08:32 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  19. 2026-09-30 20:17 UTCEG score recompute
  20. 2026-09-30 20:17 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  21. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-09-30 06:59 UTCEG score recompute
  23. 2026-09-30 06:59 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  24. 2026-09-29 15:08 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  25. 2026-09-29 01:39 UTCEG score recompute
  26. 2026-09-29 01:39 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  27. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  28. 2026-09-28 12:39 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  29. 2026-09-28 00:27 UTCEG score recompute
  30. 2026-09-28 00:27 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  31. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  32. 2026-09-27 12:15 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  33. 2026-09-27 00:03 UTCEG score recompute
  34. 2026-09-27 00:03 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  35. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  36. 2026-09-25 08:35 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  37. 2026-09-24 20:23 UTCEG score recompute
  38. 2026-09-24 20:23 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  39. 2026-09-24 08:10 UTCEG score recompute
  40. 2026-09-24 08:10 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  41. 2026-09-23 19:58 UTCEG score recompute
  42. 2026-09-23 19:58 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  43. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  44. 2026-09-23 07:22 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  45. 2026-09-22 19:11 UTCEG score recompute
  46. 2026-09-22 19:11 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  47. 2026-09-22 06:03 UTCEG score recompute
  48. 2026-09-22 06:03 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  49. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  50. 2026-09-21 17:50 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  51. 2026-09-21 05:38 UTCEG score recompute
  52. 2026-09-21 05:38 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  53. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  54. 2026-09-20 17:16 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  55. 2026-09-20 05:00 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  56. 2026-09-19 16:47 UTCEG score recompute
  57. 2026-09-19 16:47 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  58. 2026-09-19 04:35 UTCEG score recompute
  59. 2026-09-19 04:35 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  60. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  61. 2026-09-18 16:23 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  62. 2026-09-18 03:46 UTCEG score recompute
  63. 2026-09-18 03:46 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  64. 2026-09-17 15:34 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  65. 2026-09-17 03:22 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  66. 2026-09-16 15:08 UTCEG score recompute
  67. 2026-09-16 15:08 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  68. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  69. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  70. 2026-09-16 02:56 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  71. 2026-09-15 14:44 UTCEG score recompute
  72. 2026-09-15 14:44 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  73. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  74. 2026-09-15 02:31 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1
  75. 2026-09-14 14:18 UTCGHSA enrichmentGHSA-8jg2-hpxg-m9f6 · GitHub severity HIGH · GitHub CVSS 8.1

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71506?
CVE-2026-71506 is a high-severity vulnerability; its CVE record was published on August 24, 2026. Dolibarr before 24.0.0 contains an improper authorization vulnerability in the payments REST API delete endpoint that allows authenticated attackers with invoice-deletion rights to permanently delete any payment record by bypassing the intended payment-issuance rights check. Attackers can exploit…
When was CVE-2026-71506 made public?
CVE-2026-71506 was made public on August 8, 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-71506 actively exploited?
CVE-2026-71506 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71506?
CVE-2026-71506 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71506?
A fix for CVE-2026-71506 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71506 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-71506?

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

Book a Demo →Browse All CVEs