# CVE-2026-108951: LavaLite CMS through 10.1.2 Authorization Bypass via User Update API

> Authenticated low-privileged users can modify other users' accounts, including administrators, via the user update API.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/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:** 12 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-pj48-vpfx-3cj9

## What is CVE-2026-108951?

CVE-2026-108951 is a high-severity missing authorization vulnerability in lavalite cms, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

LavaLite CMS through 10.1.2 contains an authorization bypass vulnerability that allows authenticated low-privileged users to modify other users' accounts by abusing the AbstractRequest isWorkflow() check. Attackers can send a PATCH request to the user update route with a target identifier to change name, email, password, status, or mobile, including for administrators.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-108951 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108951 is a high-severity missing authorization vulnerability in lavalite cms, published on 12 Oct 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-108951 in the wild and no public exploit code.

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

## Sources

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

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