Skip to main content
CVE-2024-24213VulnerabilityPublished Updated

CVE-2024-24213: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Feb 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-26.

What to do

AI-suggested

1. Immediately restrict access to the Supabase dashboard to trusted and authenticated users only, employing strong multi-factor authentication (MFA) and role-based access controls (RBAC). 2. Monitor and audit all SQL queries executed via the /pg_meta/default/query endpoint to detect anomalous or unauthorized activity. 3. Implement network-level restrictions such as IP whitelisting and VPN access to limit dashboard exposure. 4. Consider disabling or limiting the use of the /pg_meta/default/query feature if it is not essential for business operations. 5. Stay updated with Supabase vendor communications for any forthcoming patches or security advisories addressing this issue. 6. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious SQL injection attempts targeting the dashboard. 7. Conduct regular security assessments and penetration testing focused on dashboard access and query execution features. 8. Educate administrators and users about the risks of executing arbitrary SQL queries and enforce strict operational procedures.

Description

Supabase PostgreSQL v15.1 was discovered to contain a SQL injection vulnerability via the component /pg_meta/default/query. NOTE: the vendor's position is that this is an intended feature; also, it exists in the Supabase dashboard product, not the Supabase PostgreSQL product. Specifically, /pg_meta/default/query is for SQL queries that are entered in an intended UI by an authorized user. Nothing is injected.

References

Community reviews

Loading reviews…