dbcve.org
InjectionWeakness · CWE-74

CVE-2026-7688

MEDIUM · 5.0 CVSS v3.1 Published 2026-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability was identified in Dolibarr ERP CRM up to 23.0.2. This affects the function _checkValForAPI of the file htdocs/expedition/class/expedition.class.php of the component Shipments API Endpoint. The manipulation of the argument fields leads to sql injection. The attack is possible to be carried out remotely. A high degree of complexity is needed for the attack. It is indicated that the exploitability is difficult. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

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's Shipments API endpoint (_checkValForAPI function in expedition.class.php). The 'fields' parameter is not properly sanitized before being used in SQL queries, allowing an attacker to inject malicious SQL code. The attack is remotely exploitable but requires high complexity.

MitigationUpgrade to Dolibarr version 23.0.3 or later. Alternatively, implement parameterized queries/prepared statements in the _checkValForAPI function to prevent SQL injection, or add proper input validation/sanitization for the fields parameter before constructing SQL queries.

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

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 Dolibarr installation version
    Check the version number of your Dolibarr installation. This is typically displayed on the Dolibarr login page footer, or can be found in the filehtdocs/admin/info.php or by running: grep -r 'const VERSION' /path/to/dolibarr/htdocs/core/ | head -5
    Affected if The installed version is lower than 23.0.3 (the fixed version)
  2. Verify Shipments module is enabled
    Log into Dolibarr as admin, go to Setup > Modules, and confirm whether the 'Shipments' module (expedition) is enabled and active
    Affected if The Shipments module is enabled and the version is below 23.0.3
  3. Confirm API access is enabled
    Check if the Dolibarr REST API is enabled. Go to Setup > API (or Setup > Web Services API) and verify that the API is active. Alternatively, check the file htdocs/admin/api.php for API status
    Affected if The Dolibarr API is exposed and enabled, and the version is below 23.0.3
  4. Inspect vulnerable code in expedition.class.php
    Locate the file expedition.class.php in your Dolibarr installation (typically in htdocs/expedition/class/). Open the file and search for the function _checkValForAPI. Examine how the 'fields' parameter is handled in SQL queries
    Affected if The _checkValForAPI function contains direct use of the 'fields' parameter in SQL queries without sanitization or parameterized queries, and the version is below 23.0.3

You are affected if your Dolibarr installation is version 23.0.2 or lower, the Shipments module is enabled, the API is exposed, and the expedition.class.php file contains unsanitized 'fields' parameter usage in the _checkValForAPI function.

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

Upgrade to Dolibarr version 23.0.3 or later. Alternatively, implement parameterized queries/prepared statements in the _checkValForAPI function to prevent SQL injection, or add proper input validation/sanitization for the fields parameter before constructing SQL queries.

Recommended fix Moderate confidence

Dolibarr ERP CRM 23.0.3 or later

  1. 1. Identify the current Dolibarr ERP CRM version installed in your environment
  2. 2. Download Dolibarr version 23.0.3 or later from the official Dolibarr website (https://www.dolibarr.org)
  3. 3. Create a full backup of the database and the Dolibarr installation directory
  4. 4. Test the upgrade in a non-production environment first
  5. 5. Apply the upgrade following Dolibarr's standard upgrade procedure
  6. 6. Verify the _checkValForAPI function in htdocs/expedition/class/expedition.class.php has been patched to prevent SQL injection via the fields parameter
  7. 7. Test the Shipments API endpoint to confirm normal functionality
  8. 8. Deploy to production after successful validation
Caveat Review Dolibarr 23.0.3 release notes for any breaking changes between your current version and the upgrade version; major version upgrades in Dolibarr may require database schema updates

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7688 — 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-2026-7688 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