Skip to main content
Menu
CVEs

Dolibarr ERP/CRM account takeover via SQL injection in criteria callback

Only affects Dolibarr 24.0.1 and 24.0.2 on MariaDB or MySQL. Fixed in 24.0.3.

CVE-2026-133476Published November 19, 2026, updated

8.8HighCNA
Exploited
No known exploitation
Fix
Fixed in 24.0.3
Who is exposed
Specific setups only

Summary

Dolibarr ERP/CRM has a flaw that lets a remote attacker who is logged in with only holiday read permissions extract other users' password hashes and API keys one character at a time, including an administrator's. Because the stolen API keys work as bearer credentials for the REST API, the attacker can gain full administrative control of the application.

Written by a model

Original description

In Dolibarr before 24.0.3, dolForgeSQLCriteriaCallback() in htdocs/core/lib/functions.lib.php allows account takeover because it strips only a single table-name prefix from a Universal Search Filter (sqlfilters) operand before checking it against the forbidden-field denylist (pass, pass_crypted, api_key). MariaDB and MySQL accept a two-level qualification such as schema.alias.column, so an operand of the form dolibarr.u.pass_crypted survives the check and is emitted into the WHERE clause. A remote authenticated user holding only the holiday read and readall permissions, which confer no user-management or administrative access, can use the resulting boolean oracle at GET /api/index.php/holidays to recover any user's bcrypt password hash and api_key one character at a time, including an administrator's. Because api_key is accepted directly by the REST API as a bearer credential, this yields full administrative control of the application. This bypasses the fix for CVE-2026-89012, which added only a strtolower() call and did not address prefix depth. The same denylist also omits pass_temp, which stores a password in cleartext, as well as national_registration_number, salary, birth, address, personal_mobile and note_private.

Who should check

Teams running Dolibarr ERP/CRM 24.0.1 or 24.0.2 on MariaDB or MySQL, including anyone exposing its REST API to authenticated users

Not fixed by: The earlier strtolower() fix for CVE-2026-89012 did not address prefix depth.

“Affected versions 24.0.1 and 24.0.2 ( >= 24.0.1, < 24.0.3 )”

tajapps.com

What to do

  1. Check whether your setup matches what the bug needs.

    Dolibarr 24.0.1 or 24.0.2 (before 24.0.3) Database backend is MariaDB or MySQL Attacker's account holds the holiday read and readall permissions
  2. Upgrade to a fixed version: 24.0.3.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133476 (In Dolibarr before 24.0.3, dolForgeSQLCriteriaCallback() in htdocs/core/lib/functions.lib.php allows account takeover because it strips…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133476 (entry last updated 2026-11-19):
Affected:
- Dolibarr Dolibarr ERP/CRM: fixed in 24.0.3
Fixed versions: 24.0.3.
Conditions (all must be true for the bug to be hit):
- Dolibarr 24.0.1 or 24.0.2 (before 24.0.3) (source: https://tajapps.com/advisories/TAJ-2026-002/)
- Database backend is MariaDB or MySQL (source: https://tajapps.com/advisories/TAJ-2026-002/)
- Attacker's account holds the holiday read and readall permissions (source: https://tajapps.com/advisories/TAJ-2026-002/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-133476 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133476 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Dolibarr/dolibarr/commit/725d20884d93b46f07b66a93071d3229b870865f
- https://github.com/Dolibarr/dolibarr/commit/7a04d9c970e45e15d29c91e6f5a34a262c6c51c8
- https://github.com/Dolibarr/dolibarr/releases/tag/24.0.3
- https://tajapps.com/advisories/TAJ-2026-002/
- https://github.com/Dolibarr/dolibarr/blob/24.0.3/ChangeLog
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133476
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133476"}.

Affected versions

cve.now Index

17Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.8/10CVSS 8.8
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 7

Questions about CVE-2026-133476

Is CVE-2026-133476 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The flaw in dolForgeSQLCriteriaCallback() in htdocs/core/lib/functions.lib.php allows account takeover by a remote authenticated user. On MariaDB and MySQL, a two-level qualification such as schema.alias.column is accepted, which is the setup the advisory describes.

Source: tajapps.com

Which versions are affected by CVE-2026-133476?

Dolibarr ERP/CRM: before 24.0.3.

Source: cve.now feed data

Am I affected, and how do I check?

Dolibarr 24.0.1 and 24.0.2 (versions from 24.0.1 up to but not including 24.0.3) are affected when the database backend is MariaDB or MySQL. The attacker needs an account holding only the holiday read and readall permissions. To check, compare the Dolibarr version shown in the admin interface with the database type in the Dolibarr configuration.

Source: tajapps.com

How do I fix CVE-2026-133476?

Upgrade Dolibarr to 24.0.3, the fixed version. The facts do not list vendor patch ids.

Source: tajapps.com

No corrections so far. Something wrong on this page? Report an error.