CVE-2024-40137
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 · uneditedDolibarr ERP CRM before 19.0.2-php8.2 was discovered to contain a remote code execution (RCE) vulnerability via the Computed field parameter under the Users Module Setup function.
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 confidenceDolibarr ERP CRM before version 19.0.2-php8.2 contains a Remote Code Execution (RCE) vulnerability. The vulnerability exists in the Computed field parameter within the Users Module Setup function, allowing authenticated attackers to execute arbitrary code on the server.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Dolibarr installation versionCheck the version.php file in the Dolibarr root directory, or log into the application and navigate to Setup > About to view the installed version number.Affected if The installed version is earlier than 19.0.2-php8.2 or the version cannot be determined to be 19.0.2-php8.2 or later.
-
Confirm Users Module is enabledLog into Dolibarr as an administrator, then go to Setup > Modules to locate the Users module. Verify if it is listed as active or enabled.Affected if The Users Module is enabled and accessible to the account you are using.
-
Verify access to Users Module SetupNavigate to Home > Users & Groups > Users, or access the Users Module configuration area. Attempt to access the Setup or configuration page for the Users Module.Affected if You can reach the Users Module configuration or setup area without receiving an access denied error.
-
Locate Computed field parameterWithin the Users Module Setup or configuration area, look for a field type or parameter labeled 'Computed', 'Computed Field', or similar terminology related to computed/custom fields.Affected if The Computed field parameter or functionality exists in the Users Module Setup and is available for configuration.
The environment is affected if the installed Dolibarr version is before 19.0.2-php8.2 and the authenticated user can access the Computed field parameter within the Users Module Setup.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Dolibarr ERP CRM to version 19.0.2-php8.2 or later to remediate this vulnerability. As this is an RCE, immediate patching is critical despite the medium CVSS score.
Dolibarr 19.0.2-php8.2 or later
- 1. Back up your Dolibarr ERP CRM database and files before making any changes
- 2. Download Dolibarr version 19.0.2-php8.2 or later from the official Dolibarr website or GitHub repository
- 3. Replace the existing Dolibarr installation files with the new version
- 4. Verify the Computed field functionality in the Users Module Setup works correctly after upgrade
- 5. Test that the application functions normally and there are no regressions
- 6. Monitor application logs for any suspicious activity
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40137 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-40137 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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