CVE-2026-37712
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 · uneditedAn 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/cron/class/cronjob.class.php, call_user_func_array() in function job type
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 confidenceDolibarr ERP/CRM versions 22.0.0-22.0.4 and 24.0.0-alpha contain a code injection vulnerability in the cron job scheduling component. The call_user_func_array() function in htdocs/cron/class/cronjob.class.php does not properly validate input when handling job types, allowing remote attackers to pass malicious parameters that result in arbitrary code execution 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Dolibarr versionLocate the version file. Common locations include htdocs/version.php, htdocs/core/lib/functions.lib.php, or the htdocs/admin/about.php page. Open the file or access the page to read the version number.Affected if The installed version is 22.0.0 through 22.0.4 inclusive, or is 24.0.0-alpha.
-
Verify cron module is enabledCheck the database for the cron module being active. Query the llx_const table for a row where name contains 'MAIN_ACTIVATE_CRON' or 'MODULE_CRON_ENABLED' with value '1'. Alternatively, check if the htdocs/cron directory exists and contains active configuration files.Affected if The cron module is enabled and accessible.
-
Examine vulnerable cronjob.class.phpLocate and open htdocs/cron/class/cronjob.class.php. Search for the call_user_func_array() function call within the runJobsFromJobQueue or similar job execution method. Inspect whether user-controlled input (such as job type or parameters) is passed directly to this function without sanitization.Affected if The file exists and the call_user_func_array() function receives unsanitized user input from job type or parameter fields.
-
Check cron job configuration accessReview the Dolibarr permissions configuration. Determine whether non-administrator users can access or configure cron jobs. Check the htdocs/cron/index.php or related files for access control enforcement.Affected if The cron interface is accessible to users without administrator privileges, or access controls are missing or weak.
You are affected if Dolibarr version 22.0.0-22.0.4 or 24.0.0-alpha is installed, the cron module is enabled, and the vulnerable call_user_func_array() in cronjob.class.php processes unsanitized job type input.
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.
From vendor dataRestrict access to the cron job functionality to authenticated administrators only, or disable the cron module if not required. Apply vendor patches when released. Consider network-level access controls to limit exposure of the cron interface.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-37712 — 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-2026-37712 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