CVE-2026-81730 Dolibarr 9.0.0 through 23.0.4 Path Traversal via EmailCollector Attachment Filename

High 8.8 Published Updated

Attackers can write arbitrary files via email attachment filenames, potentially executing code or corrupting documents in Dolibarr.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-81730?

CVE-2026-81730 is a high-severity path traversal vulnerability in Dolibarr Dolibarr Erp\/Crm, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-22

Which versions are affected by CVE-2026-81730?

It affects 1 product.

Products include Dolibarr Dolibarr Erp\/Crm.

How do I fix CVE-2026-81730?

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

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-81730 being exploited?

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

All Dolibarr Dolibarr Erp\/Crm vulnerabilities

Sources

Also known as GHSA-jgch-2jr2-87vj.

Is CVE-2026-81730 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free