# CVE-2026-71510: Dolibarr < 24.0.0 Users REST API SQL Injection via filter parameter

> Authenticated attackers can exploit SQL injection in the Dolibarr users REST API to extract sensitive data like salaries and password verifiers.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-5qq2-5wmp-fh5h

## What is CVE-2026-71510?

CVE-2026-71510 is a high-severity SQL injection vulnerability in dolibarr, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Dolibarr before 24.0.0 contains a SQL injection vulnerability in the users REST API that allows authenticated attackers with user-read rights to extract sensitive data by splicing unsanitized filter parameters into SQL WHERE clauses without column restrictions. Attackers can perform binary search on numeric fields and LIKE prefix iteration on string fields to recover salary figures and password verifiers omitted from normal API responses, while raw database error messages in the same endpoint enable column name enumeration.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-71510?


## How do I fix CVE-2026-71510?

No fix has been published for CVE-2026-71510 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-71510 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-71510 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71510 and fix it if it is affected.

What it is: CVE-2026-71510 is a high-severity SQL injection vulnerability in dolibarr, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-71510 exists.

Affected product: dolibarr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71510/ (Markdown: https://insights.sbomify.com/CVE-2026-71510/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71510
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71510
- OSV: https://osv.dev/vulnerability/CVE-2026-71510

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71510/
Summaries are generated and may contain mistakes; the official description above is the record.