External risk intelligence

Daptin Improper Authorization Vulnerability Allows Unauthenticated Usergroup Access

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-72575

Daptin is a headless CMS and API engine typically deployed as a backend service or web API. Because it exposes data management endpoints (CRUD operations) for user groups and other records, it is commonly configured as an internet-facing application or API service, making it reachable from the public internet in standard deployments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability affects daptin, a technology that manages data and user information. It allows unauthenticated attackers to potentially access and modify sensitive user group records. The primary concern is to confirm if our deployed instances are running this software and if they are exposed to the internet.

  • Unauthenticated users can manage user groups.
  • Critical access control flaw in user group management.
  • Verify daptin usage and external exposure.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can exploit this vulnerability by sending a request to the daptin API. Because the system fails to properly check for null user IDs when determining permissions, the attacker can impersonate a null user to gain unauthorized access and perform create, read, update, or delete operations on user group records.

  • Unauthenticated remote access required.
  • Null user ID bypasses permission checks.
  • Full CRUD access to user groups.

Live Threat

Current exploitation, exposure, and threat context

An improper authorization vulnerability could allow unauthenticated attackers to read, create, update, and delete usergroup records. This could occur when the application fails to properly validate user permissions, leading to unauthorized access to sensitive user group information.

  • Usergroup data and records.
  • Unauthorized access to usergroup data.
  • Complete CRUD access to usergroup objects.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects daptin, which often functions as an internet-facing API or backend service for content management. Security or platform teams are likely responsible for addressing this, with the first practical step being to identify all daptin instances, assess their reachability and criticality, and locate the accountable owner for remediation planning.

  • Security or platform teams own remediation.
  • Verify external reachability and criticality.
  • Plan targeted, risk-based updates.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Daptin software used for?

Daptin is a headless content management system and API engine. It is designed to act as a backend service that provides data management capabilities, allowing developers to handle user information, records, and API endpoints for various applications.

What does CWE-284 mean for CVE-2026-72575?

CWE-284 refers to an Improper Authorization weakness. In the context of this CVE, it means the software fails to properly verify who is allowed to perform specific actions. Because the permission system does not correctly handle null or empty user identifiers, it mistakenly grants unauthorized users the same privileges as a valid account.

How does an attacker trigger this vulnerability?

An attacker triggers the bug by sending specific requests to the Daptin API without providing valid authentication. The system incorrectly treats these unauthenticated requests as having a null user ID. It is important to note that actions requiring explicit execution permissions remain protected, but standard record management tasks do not.

Is my Daptin instance at high risk?

According to Halo Surface Signal, Daptin is frequently deployed as an internet-facing API service, making it reachable from the public web in many standard configurations. If your instance is exposed to the internet, it is more accessible to remote, unauthenticated actors compared to services restricted to an internal network.

What should I do first to manage this risk?

Your first step is to locate all instances of Daptin within your environment. Once identified, verify their network accessibility to see if they are reachable from the internet. Afterward, identify the responsible team for these services to coordinate a review of current permissions and plan for necessary software updates.

References