Dolibarr 16 before 16.0.5 contains an issue that allows an unauthenticated attacker to trigger a database dump and obtain access to sensitive business data. According to the provided information, exploitation is possible if a contact file exists. Successful exploitation exposes the company's customer records, prospect data, supplier information, and employee information. Based on the available description, the core weakness is the absence or failure of proper authentication on functionality that should restrict access to database export or dump capabilities.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit auxiliary module targeting Dolibarr ERP/CRM version 16.0.0 up to 16.0.4 (prior to 16.0.5). The module exploits CVE-2023-33568, a pre-authentication vulnerability that allows an unauthenticated attacker to dump the entire contact database (including customers, prospects, suppliers, and possibly employees) from a vulnerable Dolibarr instance. The exploit works by sending a crafted GET request to the endpoint '/public/ticket/ajax/ajax.php' with specific parameters, triggering the exposure of contact data in JSON format. The module then parses the response, extracts the contact information, and saves it in both JSON and CSV formats for further analysis. The code is written in Ruby and is designed to be run within the Metasploit framework. The only file present is the exploit module itself, and it is fully operational, providing a practical means to extract sensitive data from affected Dolibarr installations.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.