External risk intelligence

Daptin API SQL Injection Vulnerability Allows Data Extraction

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-77367

Daptin is a headless CMS that provides GraphQL and JSON-API endpoints. These API services are typically exposed as web-accessible interfaces to allow applications to retrieve data. Because the vulnerability exists in a core API list endpoint designed for external data interaction, it is commonly deployed as an internet-facing service.

SQL Injection

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 advisory concerns a critical vulnerability in Daptin, a headless CMS that provides API services. The issue allows unauthenticated attackers to potentially extract unauthorized data or cause system failures by manipulating API requests. The main concern at this stage is confirming if your organization utilizes Daptin and is exposed to this risk.

  • API flaw allows unauthorized data access.
  • Confirms Daptin relevance and exposure is key.
  • Assess Daptin usage and potential data impact.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by sending specially crafted requests to the Daptin API's list endpoint. By manipulating the sort parameters, an unauthenticated attacker can trick the system into executing arbitrary SQL commands. This could lead to the unauthorized extraction of sensitive data from the CMS database or cause the API to repeatedly fail, disrupting service.

  • Unauthenticated network access required.
  • Manipulate sort parameters in API requests.
  • Unauthorized data access and denial of service.

Live Threat

Current exploitation, exposure, and threat context

An unauthenticated attacker could exploit this vulnerability to extract unauthorized table data from Daptin, a GraphQL/JSON-API headless CMS. This could occur by manipulating sort values in API requests, leading to SQL injection that allows for blind or error-based data exfiltration, or by causing repeated query failures.

  • Table data could be at risk.
  • Malicious sort values in API requests.
  • Unauthorized data extraction or denial of service.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners and infrastructure teams are likely responsible for addressing this vulnerability in Daptin, a headless CMS. The first practical step is to identify all Daptin instances, determine their internet reachability and business criticality, and then locate the accountable owner to plan a risk-based remediation.

  • Identify Daptin instances and ownership.
  • Verify external reachability and business impact.
  • Plan remediation based on identified risk.

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 Daptin?

Daptin is a headless Content Management System (CMS) that serves as a backend engine for web and mobile applications. It automatically generates GraphQL and JSON-API endpoints based on your database schema, allowing developers to manage, query, and retrieve data without building custom backend infrastructure from scratch.

What does SQL injection mean for CVE-2026-77367?

This CVE involves improper input validation (CWE-20) that leads to SQL injection (CWE-89). Because the software fails to sanitize user-provided sort values in API requests, an attacker can escape the intended query structure. This allows them to append their own database commands, tricking the server into returning unauthorized information or disrupting database operations.

How can an attacker trigger this vulnerability?

An attacker triggers this by sending a crafted request to the API's list endpoint and injecting malicious content into the sorting parameter. Note that standard, well-formed API requests that do not attempt to manipulate the database column structure or include unexpected characters in the sort field will not trigger this specific flaw.

Why is this considered a high-priority risk?

Halo Surface Signal indicates that Daptin is primarily used to provide web-accessible APIs for data interaction, making these instances frequently internet-facing. Because the vulnerability is reachable over a network without requiring any authentication, it presents a significant risk if the affected server is accessible to the public.

What steps should I take if I use Daptin?

First, locate all running instances of Daptin within your environment and confirm their current version. If you are running any version prior to 0.12.30, plan to update the software to the patched version immediately. Focus your initial assessment on instances that are exposed to the internet, as these are the most accessible to external attackers.

References