Quick answers
- Is CVE-2026-71506 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-71506 being exploited in the wild.
- How severe is CVE-2026-71506?
- High severity, with a CVSS score of 8.1, published 24 August 2026.
- Which products and versions are affected?
- Dolibarr before 24.0.0.
- Is there a fix for CVE-2026-71506?
- A patch was published on 2026-08-24: Fix committed to repository with test on payment deletion permission in API Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-71506 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-71506?
- Check whether you run Dolibarr at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an improper authorization flaw in the payments REST API delete endpoint (api_paiements.class.php). The vulnerable code fails to check payment-issuance rights before allowing deletion, instead only checking invoice-deletion rights. An authenticated attacker with invoice-deletion permissions can craft API requests to delete arbitrary payment records, bypassing the intended authorization check. The attack requires valid authentication credentials and invoice-deletion role, but no additional user interaction. The fix involves adding the correct permission test for payment deletion in the API endpoint.
Affected products
- Dolibarr Dolibarr before 24.0.0
Timeline
- 2026-08-24: disclosed
- 2026-08-24: patched: Fix committed to repository with test on payment deletion permission in API