CVE-2026-72575

daptin - Authentication Bypass via Null Owner Permission Check on usergroup Objects

Published Aug 10, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
An improper authorization vulnerability in daptin through v0.12.34 allows unauthenticated remote attackers to read, create, update, and delete usergroup records. The permission check functions (CanRead, CanPeek, CanCreate, CanUpdate, CanDelete, CanRefer) in server/permission/permission.go return true whenever p.UserId equals the requesting userId, but fail to reject the null/zero reference — unlike CanExecute, which explicitly guards it.

Analysis

AI-generated

Technical impact

An improper authorization flaw exists in daptin version 0.12.34 that enables remote attackers who do not authenticate to perform full CRUD operations on usergroup records. The flaw lies in the permission functions (CanRead, CanPeek, CanCreate, CanUpdate, CanDelete, CanRefer) located in server/permission/permission.go, which grant access whenever the request’s UserId matches the record’s p.UserId, yet they do not reject a null or zero owner reference. Because usergroup objects can be created with a null owner, the lack of validation allows the attacker to bypass ownership checks, effectively obtaining unrestricted access to all usergroup entries.

Affected Systems

daptin, version 0.12.34 and earlier – the vulnerability exists in the server/permission/permission.go module of the open-source application available on the daptin GitHub repository.

Risk and Exploitability

The CVSS score of 9.1 classifies this flaw as critical, indicating the potential for complete loss of data integrity and confidentiality. The EPSS score is not reported, but the absence of a listed KEV status does not reduce the risk. The vulnerability allows unauthenticated remote attackers to trigger the flaw simply by sending HTTP requests to the usergroup API. Because the permission checks incorrectly return true when the request’s UserId equals the record’s owner ID, and they do not reject a null or zero owner reference, an attacker with a null or unauthenticated UserId can bypass ownership verification and gain full CRUD access. The likely attack vector is remote, through any exposed API endpoint that handles usergroup data, and the risk is high due to the critical severity and the availability of the flaw.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade daptin to a version newer than 0.12.34 in which the null owner permission check has been corrected.
  • If an immediate upgrade is impossible, restrict unauthenticated access to all endpoints that manipulate usergroup objects by configuring the web server or application level authentication checks so that only authenticated users can reach those routes.
  • Review the permission.go implementation to add explicit checks for non‑null owner values in all CRUD functions and replace the flawed logic with a secure authorization guard consistent with CanExecute.
  • Monitor logs for any unauthorized read, create, update, or delete attempts to usergroup tables to detect exploitation of the flaw.

Generated by OpenCVE AI on August 10, 2026 at 19:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Daptin
Daptin daptin
Vendors & Products Daptin
Daptin daptin
Type Values Removed Values Added
Description An improper authorization vulnerability in daptin through v0.12.34 allows unauthenticated remote attackers to read, create, update, and delete usergroup records. The permission check functions (CanRead, CanPeek, CanCreate, CanUpdate, CanDelete, CanRefer) in server/permission/permission.go return true whenever p.UserId equals the requesting userId, but fail to reject the null/zero reference — unlike CanExecute, which explicitly guards it. Since usergroup table rows have no user_account_id and are loaded with a null owner, an unauthenticated guest whose session UserId is null gains full CRUD access to all usergroup objects. An improper authorization vulnerability in daptin through v0.12.34 allows unauthenticated remote attackers to read, create, update, and delete usergroup records. The permission check functions (CanRead, CanPeek, CanCreate, CanUpdate, CanDelete, CanRefer) in server/permission/permission.go return true whenever p.UserId equals the requesting userId, but fail to reject the null/zero reference — unlike CanExecute, which explicitly guards it.
Type Values Removed Values Added
Description An improper authorization vulnerability in daptin through v0.12.34 allows unauthenticated remote attackers to read, create, update, and delete usergroup records. The permission check functions (CanRead, CanPeek, CanCreate, CanUpdate, CanDelete, CanRefer) in server/permission/permission.go return true whenever p.UserId equals the requesting userId, but fail to reject the null/zero reference — unlike CanExecute, which explicitly guards it. Since usergroup table rows have no user_account_id and are loaded with a null owner, an unauthenticated guest whose session UserId is null gains full CRUD access to all usergroup objects.
Title daptin - Authentication Bypass via Null Owner Permission Check on usergroup Objects
Weaknesses CWE-284
References
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
TuranSec
Published
Updated
Aug 10, 2026, 6:22 PM
Reserved
Aug 10, 2026, 10:32 AM
Status
Deferred
Published
Aug 10, 2026, 11:17 AM
Modified
Oct 24, 2026, 3:10 PM