CVE-2026-133476

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-11-20. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-130766 (ENISA EUVD) · GHSA-6m2v-gxrq-q72v (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
51st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 19, 2026

Last Modified

November 20, 2026

Advisory Details (5)

Auto-updated Nov 19, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release.
Web page

dolibarr/ChangeLog at 24.0.3 · Dolibarr/dolibarr · GitHub

https://github.com/Dolibarr/dolibarr/blob/24.0.3/ChangeLog
Web page🟡 PoC Available

TAJ-2026-002: Dolibarr ERP CRM, sqlfilters denylist bypass | TAJ APPS

https://tajapps.com/advisories/TAJ-2026-002/
GitHub release Patch Available

24.0.3

Patch available: Dolibarr/dolibarr 24.0.3

https://github.com/Dolibarr/dolibarr/releases/tag/24.0.3
GitHub commit

commit 725d20884d93 (Dolibarr/dolibarr)

Fix landed in Dolibarr/dolibarr commit 725d20884d93 — awaiting tagged release

https://github.com/Dolibarr/dolibarr/commit/725d20884d93b46f07b66a93071d3229b870865f
GitHub commit

commit 7a04d9c970e4 (Dolibarr/dolibarr)

Fix landed in Dolibarr/dolibarr commit 7a04d9c970e4 — awaiting tagged release

https://github.com/Dolibarr/dolibarr/commit/7a04d9c970e45e15d29c91e6f5a34a262c6c51c8

Vendor Advisories for CVE-2026-133476(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.6% · 51st percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  3. 2026-11-20 14:28 UTCEchelonGraph re-scored
  4. 2026-11-20 14:28 UTCGHSA enrichmentGHSA-6m2v-gxrq-q72v · GitHub severity HIGH · GitHub CVSS 8.8
  5. 2026-11-20 13:42 UTCEchelonGraph re-scored
  6. 2026-11-20 13:42 UTCGHSA enrichmentGHSA-6m2v-gxrq-q72v · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-11-20 13:28 UTCEchelonGraph re-scored
  8. 2026-11-20 13:28 UTCGHSA enrichmentGHSA-6m2v-gxrq-q72v · GitHub severity HIGH · GitHub CVSS 8.8
  9. 2026-11-20 02:38 UTCEchelonGraph re-scored
  10. 2026-11-20 02:38 UTCGHSA enrichmentGHSA-6m2v-gxrq-q72v · GitHub severity HIGH · GitHub CVSS 8.8
  11. 2026-11-19 23:04 UTCENISA EUVD ID recordedEUVD-2026-130766 · Source: ENISA EUVD
  12. 2026-11-19 22:46 UTCEchelonGraph re-scored
  13. 2026-11-19 21:33 UTCEchelonGraph re-scoredFirst assessed: 8.8 HIGH
  14. 2026-11-19 21:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-133476?
CVE-2026-133476 is a high-severity vulnerability; its CVE record was published on November 19, 2026. 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,…
When was the CVE record for CVE-2026-133476 published?
The CVE record for CVE-2026-133476 was published on November 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 20, 2026; the record at its source may have been updated since.
Is CVE-2026-133476 actively exploited?
CVE-2026-133476 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-133476?
CVE-2026-133476 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-133476?
A fix for CVE-2026-133476 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-133476 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-133476

Explore →

Is Your Infrastructure Affected by CVE-2026-133476?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.