CVE-2023-33568
Dolibarr Erp\/Crm 16.0.0 – 16.0.5
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-33568 is a high-severity Files or Directories Accessible to External Parties (CWE-552) vulnerability in Dolibarr Erp\/Crm. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Cloud Storage (T1530); ranked in the top 3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Dolibarr versions 16 prior to 16.0.5 contain an exposure issue tracked as CVE-2023-33568 that permits unauthenticated database dumping when a contact file is present. The flaw, assigned CWE-552 and rated 7.5 under CVSS 3.1, allows remote retrieval of the full set of customer, prospect, supplier, and employee records without any authentication or user interaction.
An attacker with network access can directly request the exposed contact file endpoint and obtain a complete database dump, thereby gaining the organization's entire contact and personnel data store. No privileges or prior interaction are required, making the vector available to any internet-facing instance that has not been updated.
Public references point to two corrective commits in the Dolibarr repository and an accompanying forum announcement that identify the upgrade to 16.0.5 as the required remediation. A detailed technical write-up on dsecbypass.com further describes the pre-authentication path and confirms that applying the patch eliminates the file exposure. The associated EPSS score has remained at 0.8984 since disclosure with no documented rise from a lower baseline.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-1788
Vulnerability Data
An issue in Dolibarr 16 before 16.0.5 allows unauthenticated attackers to perform a database dump and access a company's entire customer file, prospects, suppliers, and employee information if a contact file exists.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 5 hardening rules · 2 OS baselines
V8.4.2
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Controls on authorized publication limit files and directories with nonpublic data from becoming accessible to external parties.
Controlling and documenting P2P file sharing prevents files and directories from being made accessible to external parties for unauthorized distribution.
Identifying and documenting file and directory locations allows restriction of access to external parties.
Protecting backup files ensures they are not accessible to external parties or unauthorized spheres.
Sanitizing equipment before off-site maintenance reduces the risk of files or directories containing sensitive data becoming accessible to external parties.
Policy restricts media access to authorized parties only, preventing exposure of resources to external or unauthorized actors.
Media access restrictions prevent files or directories from being accessible to external parties.
Employing and evaluating controls at documented alternate sites makes files and directories less likely to be accessible to external parties through physical or environmental weaknesses.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Enforcing least-privilege permissions and authorization policies directly prevents unauthorized file/directory exposure.
Logical segmentation and access protections stop external parties from reaching files that should remain internal.
Data-at-rest protections such as encryption or ACLs reduce the impact of unintended file exposure.
Hardened configuration baselines commonly include file-system permission settings that limit external access.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
CWE-552 is the absence of access control on files/directories (web roots without restrictions, cloud storage open to public, archives exposing sensitive files); A.8.3 mandates access restriction mechanisms (configuration controls, per-user/per-identity permissions, isolation of sensitive data), so applying it where it was not applied before configures those controls and the unauthorized accessibility stops being present — nothing of the weakness is left over.
A.8.29's combined programme of code review, vulnerability scanning and penetration testing reaches CWE-552 through both SOURCE (code that places files under web root or packages archives without exclusions) and RUNTIME (probing for accessible files, scanning cloud storage configurations); the remainder is bounded and nameable — archive contents not visible in the packaging logic, and storage or container configurations outside the test environment's scope.
A.8.9's configuration monitoring and deviation correction removes the configuration-based instances of CWE-552 (cloud storage misconfigurations like 'Allow Blob Public Access' = true, IAM policies granting allUsers access, web server directory permissions), which constitute the bulk of modern instances; the remainder is the code/architecture-level instances (files placed under web root by design) that configuration management does not reach.
Graded partial by the owner: this user access lifecycle clause does not address cases where access groups and roles are not well defined, nor cases where user access provisioning is not normally applied, such as file permissions on a web server.
Training raises awareness of file placement under web roots, archive packaging hygiene, and cloud storage access configuration, and the clause specifically addresses technical teams' skills for configuring security — but CWE-552 arises from specific technical decisions (storage account flags, IAM bindings, archive exclusions) that training alone does not fully prevent, placing it closer to the CWE-598 anchor than the CWE-1428 one.
A.8.21's network service controls (authentication, authorization, network access restrictions, procedures to restrict access to network services) can block external parties from reaching the service that exposes the files, but the underlying file/directory access control weakness is at the storage layer and is not addressed by this clause.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.
Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.
No rule maps to these weaknesses at full or mostly. Tick the option above to see the partial mappings.
Oracle Linux 8 (2 partial rules)
- V-248579 OL 8 must restrict access to the kernel message buffer. blocks CWE-552
- V-248597 There must be no "shosts.equiv" files on the OL 8 operating system. blocks CWE-552