Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-81730Published 2026-08-27

CVE-2026-81730 — dolibarr

high

As of 2026-08-28, CVE-2026-81730 is a HIGH-severity vulnerability in dolibarr, CVSS v3.1 8.2, EPSS 0.3% (30.4th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-81730 as of 2026-08-28; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
8.2/10High
EPSS
0.3%Higher than 30.4% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
5.3/10Threadlinqs triage score
Published
Updated 2026-08-28
CVSS v3.1 8.2 (HIGH) · CVSS v4.0 8.8 · EPSS 0.3% (higher than 30.4% of all scored CVEs) · Priority 5.3/10 · Published 2026-08-27

Last updated:

What is CVE-2026-81730?

Dolibarr 9.0.0 through 23.0.4 saves inbound email attachments under the name supplied in the message's MIME headers without reducing it to a safe basename. The global saveAttachment() in htdocs/emailcollector/lib/emailcollector.lib.php builds $filepath = $path . $filename . '.' . $ext and hands it to file_put_contents(), and the private saveAttachment() in htdocs/emailcollector/class/emailcollector.class.php writes to $destdir.'/'.$filename; the name reaches both from the attachment's own getName() or getFilename() value by way of the record-join, create-ticket and create-project operations. A traversal sequence in the filename therefore survives intact, so any sender who can email a mailbox that an EmailCollector monitors, which is the module's ordinary use for a support or ticket inbox, can place attacker-controlled content outside the per-object attachment directory without holding a Dolibarr account. Under the hardened layout Dolibarr's SECURITY.md requires, with htdocs read-only, the write is confined to the documents tree and corrupts or forges other objects' documents; where htdocs is writable the same primitive reaches a web-executable path. Version 24.0.0 applies dol_sanitizePathName() and dol_sanitizeFileName() before the write.

The record classifies CVE-2026-81730 under weakness class CWE-22. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 84 days ago.

Severity and exploitation probability

CVSS v3.1 base score
8.2 — HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
CVSS v4.0 base score
8.8
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
EPSS (FIRST)
0.3% probability of exploitation in the next 30 days, higher than 30.4% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
5.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-08-27

Is CVE-2026-81730 being exploited?

It currently carries a trending score of 37 in the Threadlinqs vulnerability feed.

Affected products and versions

  • Dolibarr: dolibarr

How to fix CVE-2026-81730

Patch reference: https://github.com/Dolibarr/dolibarr/commit/264a44defb5e438689c75679617f6edc4c038abc. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-81730

No threat campaign in the Threadlinqs corpus currently references CVE-2026-81730, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Technical analysis

Third-party advisory

Issue tracking and product pages