# CVE-2026-82633: Dolibarr 10.0.0 before 24.0.0 Missing Authorization on REST Users Groups Endpoint

> Authenticated users can bypass authorization checks to retrieve private group membership data of other users via the REST API.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/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:** 30 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-mfxx-qcw7-5q5r

## What is CVE-2026-82633?

CVE-2026-82633 is a medium-severity missing authorization vulnerability in dolibarr, published on 30 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Dolibarr versions 10.0.0 before 24.0.0 fail to perform per-object authorization checks in the Users::getGroups REST API endpoint, allowing authenticated users to retrieve group memberships of other users. Attackers can call GET /users/{id}/groups with arbitrary user identifiers to access group names, entity associations, and private notes across tenant boundaries.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-82633 being exploited?

There is no known exploitation of CVE-2026-82633 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82633 is a medium-severity missing authorization vulnerability in dolibarr, published on 30 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82633 in the wild and no public exploit code.

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-82633/ (Markdown: https://insights.sbomify.com/CVE-2026-82633/index.md)
```

## Sources

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

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