EUVD-2026-30589Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
3DescriptionGitHub Advisory
Mathesar is a web application that makes working with PostgreSQL databases both simple and powerful. From 0.2.0 to before 0.10.0, explorations.get, explorations.replace, and explorations.delete operate on an exploration_id without verifying that the requesting user was a collaborator on the exploration’s database. An authenticated user on the same Mathesar installation who knew or guessed an exploration ID could read, replace, or delete a saved exploration belonging to a database where they were not a collaborator. This affected Mathesar-managed saved exploration definitions, including names, descriptions, selected columns, display metadata, filters, sorting, and transformations. This vulnerability is fixed in 0.10.0.
AnalysisAI
Broken access control in Mathesar 0.2.0 through 0.9.x allows authenticated users to read, modify, or delete saved explorations (database query definitions) in databases where they lack collaborator privileges. Exploitation requires only a valid user account and knowledge of an exploration ID - easily guessed or enumerated. Fixed in version 0.10.0. No public exploit identified at time of analysis, with EPSS data not available for this recently disclosed vulnerability.
Technical ContextAI
Mathesar is a PostgreSQL database management web application designed to simplify database operations through a user-friendly interface. Saved explorations are query definitions that store column selections, filters, sorts, transformations, and metadata for reuse. The vulnerability stems from CWE-639 (Authorization Bypass Through User-Controlled Key), where the explorations.get, explorations.replace, and explorations.delete API endpoints accept an exploration_id parameter but fail to verify the requesting user's role in the associated database. The application's role-based access control (RBAC) should enforce database-level collaborator permissions before allowing exploration operations, but these specific endpoints skip that verification step. This is a classic Insecure Direct Object Reference (IDOR) pattern where internal object IDs are exposed without proper authorization checks.
RemediationAI
Upgrade immediately to Mathesar 0.10.0, which implements proper authorization checks on exploration API endpoints to verify requesting users hold collaborator permissions for the associated database. The fix is confirmed by the Mathesar Foundation in their security advisory at https://github.com/mathesar-foundation/mathesar/security/advisories/GHSA-wf8r-g5rp-w69f. No workarounds exist that preserve full functionality. Temporary compensating controls for environments unable to upgrade immediately: restrict network access to the Mathesar web interface using firewall rules or reverse proxy authentication to limit the authenticated user base to fully trusted personnel only, accepting the trade-off that untrusted users cannot access the system at all. Alternatively, monitor application logs for repeated exploration API calls with sequential or unusual exploration_id patterns to detect enumeration attempts, though this provides detection rather than prevention and requires custom log analysis infrastructure.
More in PostgreSQL
View allPostgreSQL libpq functions PQescapeLiteral(), PQescapeIdentifier(), PQescapeString(), and PQescapeStringConn() improperl
An issue was discovered in Appsmith before 1.52. Rated critical severity (CVSS 9.8), this vulnerability is remotely expl
Argument injection vulnerability in PostgreSQL 9.2.x before 9.2.4, 9.1.x before 9.1.9, and 9.0.x before 9.0.13 allows re
Unauthenticated arbitrary file write in Splunk Enterprise (below 10.2.4 and 10.0.7) and Splunk Cloud Platform (below 10.
PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to incorrect authentication flaw allow
The build_tablename function in pgsql.c in the PostgreSQL (aka pgsql) extension in PHP through 5.6.7 does not validate t
A vulnerability in the h2oai/h2o-3 REST API versions 3.46.0.4 allows unauthenticated remote attackers to execute arbitra
In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_serve
## Summary An unauthenticated SQL injection vulnerability exists in the Vendure Shop API. A user-controlled query strin
Parse Server is an open source http web server backend. Rated critical severity (CVSS 10.0), this vulnerability is remot
Hard-coded default PostgreSQL credentials shipped in the docker-compose.yaml of langgenius Dify through version 1.5.1 al
A vulnerability in the FinanceChatLlamaPack of the run-llama/llama_index repository, versions up to v0.12.3, allows for
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today