# CVE-2026-125754: Dolibarr 20.0.0 through 23.0.4 and 24.x before 24.0.2 IDOR via ExpenseReport Payment API


- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-vj8j-w6v9-74w8

## What is CVE-2026-125754?

CVE-2026-125754 is a high-severity vulnerability in dolibarr, published on 10 Nov 2026. 

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-125754?


## How do I fix CVE-2026-125754?

No fix has been published for CVE-2026-125754 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-125754 being exploited?

There is no known exploitation of CVE-2026-125754 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-125754 and fix it if it is affected.

What it is: CVE-2026-125754 is a high-severity vulnerability in dolibarr, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125754 in the wild and no public exploit code.

Affected product: dolibarr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-125754/ (Markdown: https://insights.sbomify.com/CVE-2026-125754/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-125754
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-125754
- OSV: https://osv.dev/vulnerability/CVE-2026-125754

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-125754/
Summaries are generated and may contain mistakes; the official description above is the record.