Quick answers
- Is CVE-2026-108951 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108951 being exploited in the wild.
- How severe is CVE-2026-108951?
- Medium severity, with a CVSS score of 6.5, published 12 October 2026.
- Which products and versions are affected?
- LavaLite CMS through 10.1.2.
- Is there a fix for CVE-2026-108951?
- Yes: fixed in <UNKNOWN>. Until then: Restrict API access to the user update endpoint by network policy or disable the update API if not required for normal operations until a patch is available. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-108951 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-108951?
- Check whether you run LavaLite CMS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: <UNKNOWN>
Restrict API access to the user update endpoint by network policy or disable the update API if not required for normal operations until a patch is available.
Technical details
The vulnerability is a broken access control flaw in the UserResourceRequest authorization handler. Authenticated requests to PATCH /api/{trans}/{guard}/user/{user} bypass proper authorization checks due to incorrect workflow detection logic, allowing an attacker to modify any user record by specifying a different user identifier. No authentication or special privileges are needed beyond a valid user session.
Affected products
- LavaLite CMS through 10.1.2
Timeline
- 2026-10-12: disclosed: CVE-2026-108951 published