CVE-2025-70866: Improper Access Control
Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 09:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Organizations should immediately audit their LavaLite CMS installations to identify affected versions (notably 10.1.0). Until an official patch is released, administrators should implement strict network-level access controls restricting access to the /admin/login endpoint to trusted IP addresses or VPN users only. Review and enforce role-based access control policies within the CMS configuration to ensure that authentication guards verify user roles before granting admin access. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block unauthorized admin login attempts by low-privileged users. Monitor authentication logs for suspicious access patterns, especially attempts by low-privilege users to access admin endpoints. Educate users on the importance of strong, unique credentials to reduce risk of credential compromise. Once a vendor patch is available, apply it promptly and validate the fix through penetration testing or code review.
Description
LavaLite CMS 10.1.0 is vulnerable to Incorrect Access Control. An authenticated user with low-level privileges (User role) can directly access the admin backend by logging in through /admin/login. The vulnerability exists because the admin and user authentication guards share the same user provider without role-based access control verification.