dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-37711

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/actions_addupdatedelete.inc.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

A remote code execution vulnerability exists in Dolibarr ERP/CRM versions 22.0.0 through 22.0.4 and 24.0.0-alpha within the htdocs/core/actions_addupdatedelete.inc.php file. Attackers can execute arbitrary code via this endpoint without explicit authentication requirements mentioned.

MitigationApply vendor patches for Dolibarr when available; until then, restrict network access to the affected PHP endpoint via web server configuration or WAF rules to mitigate exploitation.

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 found in the Dolibarr installation root (e.g., version.php or DolibarrVersion) or check the admin panel About section
    Affected if version matches 22.0.0 through 22.0.4 or is 24.0.0-alpha
  2. Verify the vulnerable file exists
    Confirm the presence of htdocs/core/actions_addupdatedelete.inc.php in your Dolibarr installation directory
    Affected if the file exists in the expected location
  3. Check endpoint accessibility
    Inspect web server configuration to determine if the affected PHP endpoint is externally reachable (check for any rewrite rules or access control lists that may restrict access)
    Affected if the endpoint is exposed to untrusted networks without proper restrictions
  4. Review authentication configuration
    Examine Dolibarr user authentication settings and session management for the core/actions endpoints; check if anonymous or unauthenticated access is permitted
    Affected if the endpoint permits requests without valid authentication tokens
  5. Audit recent access logs
    Review web server access logs for unusual POST requests to core/actions_addupdatedelete.inc.php that may indicate exploitation attempts
    Affected if suspicious requests to this endpoint appear in logs

You are affected if your Dolibarr installation version falls within 22.0.0-22.0.4 or 24.0.0-alpha AND the vulnerable PHP file is present and accessible.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for Dolibarr when available; until then, restrict network access to the affected PHP endpoint via web server configuration or WAF rules to mitigate exploitation.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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