CVE-2025-60798 identifies a critical SQL injection vulnerability in phpPgAdmin, an open-source web-based administration tool for PostgreSQL databases. The flaw exists in the display.php script at line 396, where the application takes user input from the $_REQUEST['query'] parameter and forwards it directly to the browseQuery function without any sanitization or parameterization. This lack of input validation allows an authenticated attacker to inject malicious SQL commands, which the database executes with the privileges of the phpPgAdmin user. The vulnerability could enable attackers to read, modify, or delete database contents, escalate privileges, or even execute arbitrary commands on the underlying system if the database user has sufficient rights. Although no public exploits have been reported, the vulnerability is severe due to the direct impact on database integrity and confidentiality. The absence of a CVSS score suggests it is newly disclosed, but the technical details and attack vector indicate a high severity. The vulnerability affects phpPgAdmin versions 7.13.0 and earlier, which are widely used in managing PostgreSQL databases, especially in enterprise and governmental environments. The attack requires authentication, meaning the attacker must have valid credentials or exploit weak authentication mechanisms. The vulnerability highlights the critical need for secure coding practices, especially input validation and the use of prepared statements in database management tools.

For European organizations, this vulnerability could have severe consequences. PostgreSQL is widely used across Europe in both public and private sectors, including finance, healthcare, government, and critical infrastructure. Exploitation could lead to unauthorized data access, data corruption, or complete database compromise, resulting in data breaches, operational disruption, and regulatory non-compliance (e.g., GDPR violations). The ability to execute arbitrary SQL commands could allow attackers to extract sensitive personal data or intellectual property, manipulate financial records, or disrupt essential services. Organizations relying on phpPgAdmin for database administration are particularly at risk if they have not updated to a patched version or implemented compensating controls. The requirement for authentication somewhat limits the attack surface but does not eliminate risk, especially in environments with weak credential management or exposed phpPgAdmin interfaces. The lack of known exploits currently provides a window for proactive mitigation before widespread attacks occur.

1. Immediately upgrade phpPgAdmin to a version that addresses this vulnerability once available. If no patch is released yet, consider disabling or restricting access to phpPgAdmin interfaces. 2. Implement strict input validation and sanitization for all user inputs, especially those passed to database query functions. 3. Use web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the 'query' parameter. 4. Enforce strong authentication mechanisms, including multi-factor authentication, to reduce the risk of unauthorized access. 5. Restrict phpPgAdmin access to trusted networks or VPNs only, avoiding exposure to the public internet. 6. Regularly audit database user privileges to ensure the phpPgAdmin user has the minimum necessary rights, limiting potential damage from exploitation. 7. Monitor logs for suspicious query patterns or failed authentication attempts indicative of exploitation attempts. 8. Educate administrators on secure configuration and the risks of SQL injection vulnerabilities in management tools.