CVE-2025-67793
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn API vulnerability in DriveLock allows users with the 'Manage roles and permissions' privilege (default in Administrator role) to escalate their own or other users' privileges to the Supervisor role through a direct API call. This privilege escalation occurs because the API does not properly validate authorization for role promotion requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 24.1, <= 24.1.6>= 24.2, <= 24.2.8>= 25.1, < 25.1.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed DriveLock versionAccess the DriveLock administration console or check the software version through the About/Version information in the UI, or query the installed package version via system inventory tools if availableAffected if The installed version falls within 24.1 through 24.1.6, 24.2 through 24.2.8, or 25.1 through 25.1.5
-
Verify if the 'Manage roles and permissions' privilege existsNavigate to the DriveLock administration console, go to Role or Permission management settings, and check whether the 'Manage roles and permissions' privilege is defined or visible in the role configurationAffected if The privilege exists in the role configuration (which it does by default in Administrator role for affected versions)
-
Identify users with Administrator roleIn the DriveLock console, review the user list or user management section and identify accounts assigned the Administrator role which includes the 'Manage roles and permissions' privilegeAffected if There are any Administrator accounts present, as they can exploit this vulnerability
-
Review user accounts for unexpected Supervisor role assignmentIn the user management section, examine the assigned roles for all accounts and check if any accounts have the Supervisor role that were not explicitly created or assigned by an authorized administratorAffected if There are Supervisor role assignments that cannot be traced to deliberate, authorized administrative action
-
Check API or audit logs for role management activityReview DriveLock audit logs, API access logs, or security event logs for calls to role management endpoints, particularly requests that modify user roles or privilegesAffected if There are role modification API calls that were not initiated through the documented UI workflow or that originate from unexpected user sessions
Your environment is affected if DriveLock version is between 24.1 and 24.1.6, 24.2 and 24.2.8, or 25.1 and 25.1.5 AND any user has the Administrator role with the 'Manage roles and permissions' privilege.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped25.1.6
Apply vendor patch (25.1.6 or later) to fix the authorization bypass in the role management API. For cloud multi-tenant deployments, additionally review and restrict the 'Manage roles and permissions' privilege and implement additional access controls on role management endpoints.
DriveLock 25.1.6 or later (recommended: latest stable 25.x release)
- Identify the currently installed DriveLock version using the admin console or system information
- Confirm the version falls within the affected ranges: 24.1.x (≤24.1.6), 24.2.x (≤24.2.8), or 25.1.x (<25.1.6)
- Download DriveLock version 25.1.6 or later from the official vendor portal at drivelock.help
- Review the upgrade documentation and release notes for version 25.1.6
- Create a full backup of the current DriveLock configuration and database
- Schedule a maintenance window appropriate for the deployment type (cloud or on-prem)
- Execute the upgrade following the vendor's documented upgrade procedure
- Verify the installation by checking the new version number in the admin console
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67793 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-67793 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data