pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients. Prior to 1.1.0, the bundled CLI and web clients classified query_database statements only by their first keyword before deciding whether to display a write confirmation. SELECT INTO, data-modifying common table expressions beginning with WITH, and EXPLAIN ANALYZE of a write were treated as reads and could execute without confirmation on an allow_writes connection. Read-only connections remain protected by PostgreSQL transaction access mode, and EXPLAIN without ANALYZE and SELECT FOR UPDATE remain classified as reads.
This issue is fixed in 1.1.0.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
High
Difficult to exploit
Privileges Required
None
No privileges needed
User Interaction
Required
User action required
Impact Assessment
Confidentiality
None
No data leak
Integrity
High
Complete data modification
Availability
High
Complete denial of service
CVSS Vector v3.1
Weakness Type (CWE)
References 4
https://github.com/pgEdge/pgedge-postgres-mcp/commit/310c02809891cfaee6e4891cd7…
security-advisories@github.com
https://github.com/pgEdge/pgedge-postgres-mcp/pull/233
security-advisories@github.com
https://github.com/pgEdge/pgedge-postgres-mcp/releases/tag/v1.1.0
security-advisories@github.com
https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-5gmh-968…
security-advisories@github.com