dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-37713

HIGH · 7.3 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
An issue in Dolibarr ERP/CRM v.22.0.0 through v.22.0.4 and v.24.0.0-alpha allows a remote attacker to execute arbitrary code via the htdocs/core/class/commonobject.class.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 · moderate confidence

Remote code execution vulnerability in Dolibarr ERP/CRM affecting versions 22.0.0 through 22.0.4 and 24.0.0-alpha. The vulnerability exists in htdocs/core/class/commonobject.class.php, allowing remote attackers to execute arbitrary code via unspecified vectors in this core class file.

MitigationUpgrade to a patched version of Dolibarr beyond v22.0.4 and v24.0.0-alpha. Until then, restrict network access to the Dolibarr instance and review the commonobject.class.php for malicious input handling.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 installed Dolibarr version
    Locate the version file typically at htdocs/version.php or check the footer of the Dolibarr web interface for the version number
    Affected if The version shown is 22.0.0, 22.0.1, 22.0.2, 22.0.3, 22.0.4, or 24.0.0-alpha
  2. Confirm version range match
    If using a package manager or git, run 'git describe --tags' or check changelog files to verify the exact minor/patch version
    Affected if The installed version matches exactly 22.0.0 through 22.0.4 or 24.0.0-alpha
  3. Verify vulnerable file exists
    Check for the presence of htdocs/core/class/commonobject.class.php on the filesystem
    Affected if The file exists and is readable within the Dolibarr installation directory
  4. Determine application accessibility
    Confirm whether the Dolibarr web interface is exposed to network access or only accessible locally
    Affected if The application is accessible over a network (not localhost-only) and uses a vulnerable version

A user is affected if Dolibarr version 22.0.0 through 22.0.4 or 24.0.0-alpha is installed and the htdocs/core/class/commonobject.class.php file exists in a network-accessible deployment.

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 a patched version of Dolibarr beyond v22.0.4 and v24.0.0-alpha. Until then, restrict network access to the Dolibarr instance and review the commonobject.class.php for malicious input handling.

Recommended fix Moderate confidence

Dolibarr v22.0.5 or later (or latest stable v22.x/v24.x)

  1. 1. Backup your current Dolibarr installation and database before proceeding with any upgrade.
  2. 2. Download Dolibarr v22.0.5 or later (or the latest stable v22.x release) from the official Dolibarr website or GitHub repository.
  3. 3. Replace the htdocs/core/class/commonobject.class.php file with the version from the fixed release.
  4. 4. Alternatively, upgrade your entire Dolibarr installation to v22.0.5+ or the latest stable version to ensure all security patches are applied.
  5. 5. Verify the upgrade by logging in and testing core functionality.
  6. 6. Review Dolibarr release notes for the fixed version to confirm the code injection vulnerability (CVE-2026-37713) is addressed.
Caveat Review Dolibarr changelog for potential breaking changes between your current version and the upgrade target

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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