CVE-2025-67793: DriveLock · Improper Privilege Management
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in 25.1.6 : patch affected systems as a priority.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 25.1.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Dec 2025
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
To mitigate CVE-2025-67793, European organizations should immediately audit user roles and permissions within DriveLock, particularly focusing on users with the 'Manage roles and permissions' privilege. Restrict this privilege to the minimum number of trusted administrators and monitor for any unusual role changes or promotions. Implement strict API access controls and logging to detect unauthorized privilege escalations. Where possible, isolate critical workloads and sensitive data to reduce the blast radius of a compromised account. Regularly review and update security policies to enforce least privilege principles. Additionally, conduct security awareness training for administrators to recognize and report suspicious activities. Engage with DriveLock support to obtain guidance on interim fixes or workarounds. Finally, integrate this vulnerability into incident response plans to ensure rapid containment if exploitation is detected.
Description
An issue was discovered in DriveLock 24.1 through 24.1.*, 24.2 through 24.2.*, and 25.1 before 25.1.6. Users with the "Manage roles and permissions" privilege can promote themselves or other DOC users to the Supervisor role through an API call. This privilege is included by default in the Administrator role. This issue mainly affects cloud multi-tenant deployments; on-prem single-tenant installations are typically not impacted because local admins usually already have Supervisor privileges.