Dolibarr 20.0.0 through 23.0.4 and 24.x before 24.0.2 IDOR via ExpenseReport Payment API
Affects Dolibarr 20.0.0 through 23.0.4 and 24.x before 24.0.2 for accounts with expense report read and create rights. Fixed in 24.0.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 24.0.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects Dolibarr 20.0.0 through 23.0.4 and 24.x before 24.0.2 Attacker has expense report read and create rights (ExpenseReport API payment endpoints)
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Dolibarr versions 20.0.0 through 23.0.4 and 24.x before the 24.0.2 fix contain an insecure direct object reference flaw in the expense report payment API that lets a logged-in user with basic expense report rights read, create, or modify other users' payments and so falsify reimbursement records. The flaw can be reached remotely over the network, but it requires a low-privilege login.
Read the original description
Dolibarr 20.0.0 through 23.0.4 and 24.x before 24.0.2 contains an insecure direct object reference vulnerability in api_expensereports.class.php payment endpoints that lets authenticated users access other users' expense report payments. Attackers with only expense report read and create rights can call getAllPayments, getPayments, addPayment, or updatePayment to read, create, or modify payments, falsifying reimbursement state.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affects Dolibarr 20.0.0 through 23.0.4 and 24.x before 24.0.2 Attacker has expense report read and create rights (ExpenseReport API payment endpoints)Upgrade to a fixed version: 24.0.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-125754 (Dolibarr 20.0.0 through 23.0.4 and 24.x before 24.0.2 IDOR via ExpenseReport Payment API), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-125754 (entry last updated 2026-11-10): Affected: - Dolibarr dolibarr: from 20.0.0, through 23.0.4; from 24.0.0, fixed in 24.0.2 Fixed versions: 24.0.2. Conditions (all must be true for the bug to be hit): - Affects Dolibarr 20.0.0 through 23.0.4 and 24.x before 24.0.2 (source: https://www.vulncheck.com/advisories/dolibarr-20.0.0-through-23.0.4-and-24-x-before-24.0.2-idor-via-expensereport-payment-api) - Attacker has expense report read and create rights (ExpenseReport API payment endpoints) (source: https://www.vulncheck.com/advisories/dolibarr-20.0.0-through-23.0.4-and-24-x-before-24.0.2-idor-via-expensereport-payment-api) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, low-privilege login, no user action. CISA KEV: CVE-2026-125754 is not listed as of cve.now's last read. This KEV status is for CVE-2026-125754 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/Dolibarr/dolibarr/pull/40473 - https://github.com/Dolibarr/dolibarr/commit/322026099df5cffcca2fd45dd76193fca601cfd9 - https://github.com/Dolibarr/dolibarr/commit/afc12abbd24a1560aee04356e840d5819a1169fd - https://github.com/Dolibarr/dolibarr/issues/40687 - https://github.com/Dolibarr/dolibarr/blob/24.0.1/htdocs/expensereport/class/api_expensereports.class.php#L959-L968 - https://www.vulncheck.com/advisories/dolibarr-20.0.0-through-23.0.4-and-24-x-before-24.0.2-idor-via-expensereport-payment-api Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-125754 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125754.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Dolibarr dolibarr
From 20.0.0 · through 23.0.4; From 24.0.0 · fixed in 24.0.2
Evidence 8
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 6
- Patch
- Patch
- Patch
- Report
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125754
Is CVE-2026-125754 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The ExpenseReport Payment API does not check that a payment belongs to the caller, so an authenticated user can read, create, or modify other users' expense report payments. This can falsify reimbursement state.Source: vulncheck.com
Which versions are affected by CVE-2026-125754?
dolibarr: from 20.0.0 through 23.0.4; from 24.0.0 before 24.0.2.Source: cve.now feed data
Am I affected, and how do I check?
Affected versions are Dolibarr 20.0.0 through 23.0.4 and 24.0.0 before 24.0.2. The bug needs an account with expense report read and create rights that can call the ExpenseReport payment endpoints, so check the installed version and the rights granted to accounts.Source: vulncheck.com
How do I fix CVE-2026-125754?
Upgrade to Dolibarr 24.0.2 or later.Source: vulncheck.com