dbcve.org
Dolibarr Erp\/crmApplication · Dolibarr

CVE-2018-25357

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-23
Fix available
A fix is available. Upgrade to after 7.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
Dolibarr ERP CRM 7.0.3 contains a remote code execution vulnerability that allows unauthenticated attackers to execute arbitrary code by injecting PHP code through the db_name parameter. Attackers can send a POST request to install/step1.php with malicious PHP code in the db_name parameter, then execute commands via the check.php endpoint using the cmd GET parameter.

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

Dolibarr ERP CRM 7.0.3 allows unauthenticated remote code execution through PHP code injection in the db_name parameter during the installation process (install/step1.php). After injecting malicious PHP code, attackers can execute arbitrary commands via the check.php endpoint using the cmd GET parameter.

MitigationUpgrade to the latest patched version of Dolibarr and ensure the install directory is removed or access-restricted after initial setup. If already exploited, conduct a full forensic review and rebuild the environment.

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:<= 7.0.3

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
High

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

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 and version
    Check your web server for Dolibarr files (typically in web root). Look for a file containing version information, such as a version.php file or DoliVersion constant. Compare the installed version number to the affected range (7.0.3 and below).
    Affected if Dolibarr version 7.0.3 or lower is installed.
  2. Verify install directory accessibility
    Attempt to access the /install/ directory on your web server via HTTP/HTTPS without authentication. Check if install/step1.php is reachable.
    Affected if The install/ directory and install/step1.php are publicly accessible without authentication.
  3. Check for presence of check.php
    Locate check.php in the web-accessible Dolibarr directory. Attempt to access it via HTTP/HTTPS to confirm it exists and responds.
    Affected if The check.php file exists and is accessible via the web.
  4. Inspect database configuration for injected code
    Examine your database configuration file (commonly conf.php or similar) for any suspicious PHP code, base64 encoded strings, or unexpectedeval() or shell_exec() calls in the db_name or related parameters.
    Affected if The database configuration contains suspicious PHP code or encoded commands.
  5. Review web server access logs
    Search access logs for POST requests to install/step1.php with unusual db_name values, and GET requests to check.php with cmd parameters containing shell commands.
    Affected if Suspicious requests to install/step1.php or check.php with cmd parameters appear in logs.

A user is affected if Dolibarr version 7.0.3 or lower is installed AND the install/ directory or check.php endpoint are accessible over the network without authentication.

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
Upgrade available Upgrade to a release after 7.0.3
Interim mitigation

Upgrade to the latest patched version of Dolibarr and ensure the install directory is removed or access-restricted after initial setup. If already exploited, conduct a full forensic review and rebuild the environment.

Recommended fix Moderate confidence

Dolibarr ERP/CRM version 7.0.4 or later (latest stable release)

  1. 1. Back up your current Dolibarr installation and database before making any changes
  2. 2. Download the latest stable version of Dolibarr ERP/CRM from the official dolibarr.org website
  3. 3. Upgrade your Dolibarr installation to version 7.0.4 or later (preferably the latest stable release)
  4. 4. Verify the installation completes successfully
  5. 5. Confirm that the install/step1.php and check.php endpoints are no longer accessible to unauthenticated users
  6. 6. Test that the application functions normally after the upgrade
Caveat Minor version upgrades within the 7.x line typically have minimal breaking changes, but test in a staging environment first

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

Fix this in Dolibarr Erp\/crm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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