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… (CVE-2026-81730)
Description
Dolibarr versions 9.0.0 through 23.0.4 have a vulnerability in their EmailCollector module where inbound email attachments are saved using the filename supplied in the MIME headers without sanitization. This allows a malicious sender to craft filenames with directory traversal sequences, potentially writing files outside the intended attachment directory. Under secure configurations with htdocs read-only, the impact is limited to corrupting or forging documents in the documents tree. However, if htdocs is writable, this can lead to files being placed in web-executable paths. Version 24.0.0 addresses this by sanitizing filenames before saving.
CVSS v3.1
Score 8.2high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Dolibarr versions 9.0.0 through 23.0.4 save inbound email attachments using the filename provided in the MIME headers without reducing it to a safe basename. The saveAttachment() functions in the EmailCollector module directly use these filenames, allowing directory traversal sequences to remain intact. Consequently, an attacker who can send email to a mailbox monitored by EmailCollector can write files outside the intended attachment directory without needing a Dolibarr account. Under hardened security layouts with htdocs read-only, writes are confined to the documents tree, affecting document integrity. If htdocs is writable, the vulnerability can lead to placing files in web-executable locations. Dolibarr 24.0.0 mitigates this by applying dol_sanitizePathName() and dol_sanitizeFileName() to filenames before writing.
Potential Impact
This vulnerability allows unauthenticated attackers to write files outside the designated attachment directory by exploiting directory traversal in attachment filenames. The impact includes potential corruption or forgery of documents within the documents tree under secure configurations. If the htdocs directory is writable, attackers may place files in web-executable paths, increasing the risk of remote code execution or further compromise. The CVSS score of 8.2 reflects high severity due to the ease of exploitation (network vector, no privileges or user interaction required) and the high integrity impact.
Mitigation Recommendations
Dolibarr version 24.0.0 includes a fix that sanitizes attachment filenames before saving, preventing directory traversal. Users should upgrade to version 24.0.0 or later to remediate this vulnerability. If upgrading is not immediately possible, ensure that the htdocs directory is set to read-only to limit the impact to the documents tree and prevent writes to web-executable paths. Patch status is not explicitly confirmed beyond the mention of version 24.0.0 applying sanitization functions; check the official Dolibarr advisory for the latest remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-jgch-2jr2-87vj
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-81730"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a91a858acd9273b490696b8
Added to database: 08/28/2026, 15:25:12 UTC
Last enriched: 09/08/2026, 05:52:09 UTC
Last updated: 10/11/2026, 06:48:19 UTC
Views: 20
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.