# CVE-2026-108712: SuiteCRM through 7.15.2 and 8.10.2 Missing Authorization via DetailUserRole Entry Point

> Authenticated non-admin users can view other users' ACL data by manipulating the record parameter in the DetailUserRole entry point.

- **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:** 11 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-qhw8-6crf-m6jv

## What is CVE-2026-108712?

CVE-2026-108712 is a medium-severity missing authorization vulnerability in SuiteCRM, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SuiteCRM through 7.15.2 and 8.10.2 contains a missing authorization vulnerability in the DetailUserRole entry point that allows authenticated non-admin users to view other users' ACL data. Attackers can supply another non-admin user's id in the record parameter to read that user's assigned roles and per-module ACL action matrix.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-108712 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108712 is a medium-severity missing authorization vulnerability in SuiteCRM, published on 11 Oct 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-108712 exists.

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

## Sources

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

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