Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-81730 – Path Traversal / Arbitrary File Write – Dolibarr ERP/CRM 9.0.0 through 23.0.4

Be the first to know when new zero-days emerge:

Summary

CVE-2026-81730 is a path traversal vulnerability in Dolibarr ERP/CRM’s EmailCollector module, rated HIGH severity. It stems from insufficient sanitization of email attachment filenames when the application saves inbound mail attachments, allowing an attacker to write files outside the intended attachment directory. Any Dolibarr instance configured to fetch mail via EmailCollector from a mailbox reachable by external senders is exposed.

Technical details

  • Root cause: the saveAttachment() logic in htdocs/emailcollector/lib/emailcollector.lib.php (and emailcollector.class.php) builds the destination file path by directly concatenating the attachment filename taken from the email’s MIME headers, without stripping directory traversal sequences (e.g. ../).
  • Trigger condition: EmailCollector must be configured to retrieve messages from a mailbox that can receive mail from an untrusted sender; the attacker sends an email with a crafted attachment filename.
  • Attack vector: Network — no authentication to the Dolibarr application itself is required, only the ability to deliver an email to the monitored mailbox.
  • Impact: files can be written outside the intended attachment storage location; if the web root (htdocs) is writable by the process, this can lead to placement of web-executable content and potential remote code execution. At minimum it enables unauthorized file writes/overwrites.

Affected software

  • Dolibarr ERP/CRM versions 9.0.0 through 23.0.4 (EmailCollector module enabled)
  • Fixed in Dolibarr 24.0.0, which applies dol_sanitizePathName() and dol_sanitizeFileName() to attachment filenames

Severity

  • CVSS v3.1 Base Score: 8.2 (HIGH)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Mitigation and recommended actions

  • Immediate: Upgrade Dolibarr to version 24.0.0 or later, which sanitizes attachment filenames before writing them to disk.
  • If immediate patching is not possible:
    • Disable the EmailCollector module, or disable any collector jobs configured to fetch attachments from mailboxes that accept mail from untrusted/external senders.
    • Ensure the web server user cannot write to web-executable directories (htdocs) to limit the impact of any file write.
    • Restrict which mailboxes are polled by EmailCollector to trusted, internal senders only until patched.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge