CVE-2026-125754 · Package
NO FIX YET · SEE WHAT TO DO
Dolibarr's expense report API payment endpoints do not check ownership, so a logged-in user with basic expense report rights can read, create or modify payments on other users' reports. An attacker can use this to falsify reimbursement records.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Companies that run Dolibarr with the REST API enabled and give users expense report read and create rights. Users need an account first, so instances without the API or with tightly restricted accounts are lower risk.
Not affected if api-disabled, no-expense-report-rights, versions-outside-range
Who cares dolibarr, rest-api, self-hosted
htdocs/filefunc.inc.php file.24.0.2 or later on the 24.x line.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.
This page as .md ·
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.