Skip to main content
VulnerabilityPublished

CVE-2026-125754: dolibarr · Insecure Direct Object Reference

Affects dolibarrSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 24.0.2 soon.

Data as of 10 Nov 2026, 15:34 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.07.1
CNA (VulnCheck)CVSS 3.17.1
Patch
Available – fixed in 24.0.2
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade dolibarr to 24.0.2.

Affected software

ProductAffectedFixed in
DolibarrdolibarrAffected
  • >=20.0.0 <=23.0.4
  • >=24.0.0 <24.0.2
Fixed in
  • 24.0.2
GitHubdolibarrpkg:github/dolibarrOther threatsAffected
  • >=20.0.0 <=23.0.4
  • >=24.0.0 <24.0.2
Fixed in
  • 24.0.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Dolibarr to version 24.0.2 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated by the vendor advisory.

Description

Dolibarr versions 20.0.0 through 23.0.4 and 24.x before 24.0.2 have an insecure direct object reference vulnerability in the expense report payment API endpoints. Authenticated users with read and create rights on expense reports can access and manipulate other users' payment data, including reading, creating, or modifying payments and falsifying reimbursement states. This issue is fixed in version 24.0.2.

References

Community reviews

Loading reviews…