dbcve.org
Dolibarr Erp\/crmApplication · Dolibarr

CVE-2024-5314

CRITICAL · 9.1 CVSS v3.1 Published 2024-05-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerabilities in Dolibarr ERP - CRM that affect version 9.0.1 and allow SQL injection. These vulnerabilities could allow a remote attacker to send a specially crafted SQL query to the system and retrieve all the information stored in the database through the parameters sortorder y sortfield in /dolibarr/admin/dict.php.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Dolibarr ERP-CRM version 9.0.1. The sortorder and sortfield parameters in /dolibarr/admin/dict.php are not properly sanitized, allowing remote attackers to inject malicious SQL queries and potentially exfiltrate all database contents.

MitigationUpdate Dolibarr to the latest patched version. If immediate patching is not possible, implement WAF rules to block SQL injection attempts and restrict admin page access to trusted IPs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dolibarr Erp\/crmApplication
Affected:= 9.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Dolibarr version
    Check the Dolibarr version file (version.php) in thehtdocs directory, or access the About page in the Dolibarr interface under Menu > Home > About. Look for the exact version number.
    Affected if The installed version is exactly 9.0.1 (note: only this specific version is affected per the CVE)
  2. Locate the vulnerable script
    Check if the file /dolibarr/admin/dict.php exists on the web server. This is the script containing the vulnerable parameters.
    Affected if The dict.php file exists in the admin directory and is accessible via the web interface
  3. Verify the admin interface is accessible
    Attempt to access /dolibarr/admin/dict.php via HTTP/HTTPS request (requires admin credentials). Observe if the page loads and accepts sortorder/sortfield GET parameters.
    Affected if The admin dict.php page is accessible and accepts user-controlled input for sortorder and sortfield parameters without sanitization
  4. Test for SQL injection presence
    Use a browser or curl to send a request with a SQL injection payload in the sortorder or sortfield parameter, such as: ?sortfield=test' OR '1'='1. Observe for database errors or unexpected behavior.
    Affected if The application returns SQL errors or displays unexpected data indicating the input is being interpreted as SQL rather than a sort field name

A user is affected if they are running Dolibarr version 9.0.1 AND the /dolibarr/admin/dict.php page is accessible, as only this specific version contains the unsanitized sortorder/sortfield parameters in that script.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Dolibarr to the latest patched version. If immediate patching is not possible, implement WAF rules to block SQL injection attempts and restrict admin page access to trusted IPs.

Recommended fix Moderate confidence

Upgrade to the latest stable Dolibarr version (currently 19.x or 20.x series)

  1. 1. Back up your current Dolibarr installation and database before attempting any upgrade
  2. 2. Download the latest stable version of Dolibarr from the official repository (dolibarr.org)
  3. 3. Review the upgrade documentation for your specific version path at https://docs.dolibarr.org/
  4. 4. Perform the upgrade following standard Dolibarr upgrade procedures
  5. 5. Verify that the /dolibarr/admin/dict.php page functions correctly after upgrade
  6. 6. Test that the sortorder and sortfield parameters in dict.php no longer accept SQL injection payloads
  7. 7. Confirm your installation is running the upgraded version
Caveat Review Dolibarr release notes between 9.0.1 and target version for any breaking changes in modules, customizations, or database schema

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dolibarr Erp\/crm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5314 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5314 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data