Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Dolibarr account with member-read rights
-
DeliveryQuery Members REST API list or detail endpoint
-
ExploitReceive bcrypt hash fields in JSON response
-
ExecutionExport hashes for offline processing
-
PersistRun dictionary or rule-based cracking tool
-
ImpactCompromise member accounts with weak passwords
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V6 - Authentication Credential protection in transit/storage
|
| Exploitation Conditions | Exploitation requires an active authenticated session in Dolibarr with at minimum the member-read role, which is a low-privilege built-in role within the platform. The Members REST API module must be active and network-accessible, which is a standard configuration for Dolibarr deployments that expose the REST API. No non-default configuration, special protocol, or elevated privilege beyond member-read is required to trigger the data exposure. Exploitation is bounded by the authentication requirement (PR:L per CVSS 4.0): unauthenticated external attackers cannot directly exploit this flaw without first obtaining credentials. Downstream impact is further constrained by the bcrypt work factor, meaning accounts with strong passwords present a significantly higher cracking cost. No user interaction is required once the attacker holds a qualifying session. |
| Impact | The CVSS 4.0 score of 7.1 with vector AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N reflects an accurate picture: the vulnerability is network-reachable, requires no special attack conditions, and demands only low-privilege authentication, with high confidentiality impact limited to the vulnerable system. The CVSS metrics are internally consistent with the description - a low-trust authenticated user (PR:L) can retrieve credential material over the network (AV:N) with no complexity (AC:L). No EPSS data was supplied, so exploitation probability cannot be quantified precisely; however, the confirmed availability of a public proof-of-concept meaningfully elevates practical risk beyond the theoretical. The absence of a CISA KEV listing suggests no confirmed widespread in-the-wild exploitation at time of analysis, but the low exploitation bar (any member-read account) and available exploit code mean this should not be deprioritized as a merely theoretical finding. Real-world impact is gated on password strength: bcrypt is computationally expensive, so organizations enforcing strong password policies have partial natural mitigation, but this should not substitute for patching. |
| Exploit ScenarioDerived | An authenticated attacker with a low-privilege Dolibarr account that holds member-read rights issues a GET request to the Members API list endpoint, receiving a JSON response that includes the bcrypt password hash for every member. The attacker exports these hashes and submits them to an offline cracking tool such as Hashcat with a rockyou-derived wordlist and common rule sets. Accounts protected by weak or reused passwords are compromised within hours, potentially including administrator accounts if those users are also registered as members, granting the attacker escalated access within Dolibarr or connected systems. A public proof-of-concept demonstrating this technique is available per the cveorg exploit reference. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 24, 2026
Dolibarr's Members REST API before version 24.0.0 exposes bcrypt password hash verifiers to any authenticated user holding member-read rights, enabling offline password cracking attacks against member accounts. Both the member list and individual member detail endpoints return the crypted password verifier field because neither the base API serializer nor the Members API class applies field-level filtering to strip credential material from responses. A public proof-of-concept exists; this is not confirmed as actively exploited via CISA KEV, but the low access bar combined with exposed credential hashes and available exploit code makes this a genuine remediation priority for organizations running affected versions.
RemediationAI
The primary fix is to upgrade to Dolibarr 24.0.0 or later; the underlying code change is captured in commit b1691356eb96d962833e5c7325c9e58e6823c78d, which adds filtering to prevent password verifier fields from being serialized in API responses. The release is available at https://github.com/Dolibarr/dolibarr/releases/tag/24.0.0. If immediate upgrade is not feasible, restrict network access to the Members REST API endpoints at the perimeter or application firewall, blocking requests to member list and member detail routes for all but trusted administrative sources - note this may break legitimate API integrations that depend on member data. Additionally, audit and minimize which accounts hold member-read rights, revoking the role from any user who does not operationally require it, to reduce the pool of potential exploiters. Enforcing strong, unique passwords for all member accounts increases the cost of offline cracking but is not a substitute for patching.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Dolibarr is an open-source ERP and CRM platform commonly deployed by SMBs, non-profits, and associations. The affected component is the Members REST API, which serializes member records from the database without stripping the password verifier field before transmission. CWE-522 (Insufficiently Protected Credentials) identifies the root cause: the application fails to protect stored credentials from disclosure by omitting field-level output filtering in the API serialization layer. The CPE cpe:2.3:a:dolibarr:dolibarr:*:*:*:*:*:*:*:* encompasses all product versions prior to 24.0.0. Although bcrypt hashes incorporate a work factor that makes brute-force cracking expensive, they remain vulnerable to targeted offline dictionary attacks and rule-based cracking tools such as Hashcat, particularly for accounts using weak or common passwords.
Know when Dolibarr gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
REST API is network-reachable (AV:N), no special conditions (AC:L), low-privilege auth required (PR:L), no scope change, only credential hash disclosure with no integrity or availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Dolibarr before 24.0.0 contains a sensitive data exposure vulnerability in the Members REST API that allows authenticated attackers with member-read rights to retrieve bcrypt password verifiers by querying member endpoints. Attackers can call the individual member or member list endpoints to obtain crypted password verifier fields that are not filtered by the base API serializer or the Members API class, potentially enabling offline password cracking attacks.
Executive ViewAI
Dolibarr's Members REST API before version 24.0.0 exposes bcrypt password hashes to authenticated users with member-read permissions. Publicly available exploit code exists, though no active exploitation has been confirmed via CISA KEV tracking. The credential exposure combined with permissive access requirements and available exploit code creates a material password-cracking risk to member accounts, warranting immediate patching prioritization.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
An issue in Dolibarr ERP CRM v.17.0.1 and before allows a remote privileged attacker to execute arbitrary code via a cra
Dolibarr before 17.0.1 allows remote code execution by an authenticated user via an uppercase manipulation: <?PHP instea
Dolibarr ERP/CRM 4.0.4 has SQL Injection in doli/theme/eldy/style.css.php via the lang parameter. Rated critical severit
Cross Site Scripting vulnerability in Dolibarr ERP CRM v.17.0.1 and before allows a remote attacker to obtain sensitive
Dolibarr ERP/CRM 4.0.4 stores passwords with the MD5 algorithm, which makes brute-force attacks easier. Rated critical s
SQL injection attacks can result in unauthorized access to sensitive data, such as passwords, credit card details, or pe
Dolibarr Open Source ERP & CRM for Business before v14.0.1 allows attackers to escalate privileges via a crafted API. Ra
Dolibarr ERP & CRM <=15.0.3 is vulnerable to Eval injection. Rated critical severity (CVSS 9.8), this vulnerability is r
The website builder module in Dolibarr 13.0.2 allows remote PHP code execution because of an incomplete protection mecha
The htdocs/index.php?mainmenu=home login page in Dolibarr 10.0.6 allows an unlimited rate of failed authentication attem
SQL injection vulnerability in Dolibarr before 7.0.2 allows remote attackers to execute arbitrary SQL commands via vecto
Dolibarr ERP CRM 7.0.3 contains a remote code evaluation vulnerability that allows unauthenticated attackers to execute
EUVD-2026-65084
GHSA-589q-6598-2vqx
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB