CVE-2024-24213
Supabase Postgres SQL injection
- Published8 Feb 2024
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
Frequently asked
Is CVE-2024-24213 being actively exploited?
CVE-2024-24213 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.07%.
How severe is CVE-2024-24213?
CVE-2024-24213 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 1.07% probability of exploitation.
Which products are affected by CVE-2024-24213?
Affected products include Supabase Postgres.
How do I fix CVE-2024-24213?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-24213 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.