Dolibarr ERP/CRM authorization bypass in event attendees API
- Exploited
- No known exploitation
- Fix
- Fixed in 24.0.3
- Who is exposed
- Not reported
Summary
Dolibarr ERP/CRM versions from 22.0.0 up to (but not including) the fixed release have an API endpoint for event attendees that returns attendee and project data without checking the caller's permissions. A remote user with a low-privilege login can extract column values one character at a time.
Written by a model
Original description
In Dolibarr before 24.0.3, /api/index.php/eventattendees discloses attendee and project data regardless of the caller's permissions. Only 22.0.0 and later (where api_eventattendees.class.php exists) are affected. A remote authenticated user can obtain column values one character at a time.
What to do
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-133481 (In Dolibarr before 24.0.3, /api/index.php/eventattendees discloses attendee and project data regardless of the caller's permissions.), 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-133481 (entry last updated 2026-11-19):
Affected:
- Dolibarr Dolibarr ERP/CRM: from 22.0.0, fixed in 24.0.3
Fixed versions: 24.0.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133481 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133481 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/1f5dbb010ce2be58d6deee68564094822ec761b7
- https://github.com/Dolibarr/dolibarr/releases/tag/24.0.3
- https://tajapps.com/advisories/TAJ-2026-001/
- 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-133481
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-133481"}.Affected versions
- Dolibarr Dolibarr ERP/CRMFrom 22.0.0 · fixed in 24.0.3
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.3/10CVSS 4.3
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133481 |
| Record | NVD · CVE-2026-133481 |
| Other links 4 | |
| Patch | GitHub · Dolibarr/dolibarr · Commit 1f5dbb01 |
| Repository | GitHub · Dolibarr/dolibarr · Release 24.0.3 |
| Repository | GitHub · Dolibarr/dolibarr · ChangeLog |
| Link | tajapps.com · advisories/TAJ-2026-001 |
Questions about CVE-2026-133481
Is CVE-2026-133481 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
Which versions are affected by CVE-2026-133481?
Dolibarr ERP/CRM: from 22.0.0 before 24.0.3.
Source: cve.now feed data
How do I fix CVE-2026-133481?
Upgrade to a fixed version: 24.0.3.
Source: cve.now feed data
Related
- CVE-2026-133476In Dolibarr before 24.0.3, dolForgeSQLCriteriaCallback() in htdocs/core/lib/functions.lib.php allows account takeover because it strips…
- CVE-2019-25452Dolibarr ERP/CRM 10.0.1 SQL Injection via elemid
- CVE-2026-22666Dolibarr ERP/CRM < 23.0.2 Authenticated RCE via dol_eval_standard()
- CVE-2019-25450Dolibarr ERP/CRM 10.0.1 SQL Injection via card.php
- CVE-2026-118754Dolibarr ERP CRM before 24.0.2 Missing Authorization via public recruitment view.php
- CVE-2026-33944Dolibarr: SQL Injection in societe/class/societe.class.php via localtax1_value parameter
No corrections so far. Something wrong on this page? Report an error.