Skip to main content
VulnerabilityPublished

CVE-2026-89037: 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 13 Nov 2026, 20:48 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.16.5
Patch
Available – fixed in 24.0.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 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 13 Nov 2026.

What to do

Upgrade dolibarr to 24.0.2.

Affected software

ProductAffectedFixed in
DolibarrdolibarrAffected
  • <24.0.2
Fixed in
  • 24.0.2
GitHubdolibarrpkg:github/dolibarrOther threatsAffected
  • <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 authorization bypass vulnerability has been fixed. No additional mitigations are required once the official fix is applied.

Description

Dolibarr versions prior to 24.0.2 have an insecure direct object reference vulnerability in the REST Documents API for the ticket module. Authenticated API users with ticket read permission can access attachments of tickets belonging to other companies by bypassing company-scope checks that are only applied during public ticket authentication, which REST API authentication does not perform. This allows enumeration of ticket identifiers and unauthorized retrieval of sensitive documents such as invoices and contracts.

References

Community reviews

Loading reviews…