Skip to main content
VulnerabilityPublished

CVE-2025-60799: phppgadmin · Improper Access Control

Affects phppgadminSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 09:15 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2025

  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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubphppgadmin/phppgadminpkg:github/phppgadmin/phppgadminOther threatsAffected
  • <=7.13.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately review their phpPgAdmin deployments and restrict access to trusted administrators only, ideally limiting access via VPN or internal networks. Implement web application firewalls (WAFs) with rules to detect and block suspicious parameter manipulation targeting sql.php. Monitor session variables and logs for unusual activity indicative of session poisoning or injection attempts. Until an official patch is released, consider disabling or restricting the vulnerable sql.php functionality if feasible. Educate users to avoid clicking untrusted links that could trigger malicious parameter injection. Employ Content Security Policy (CSP) headers to mitigate the impact of stored XSS attacks. Regularly update phpPgAdmin to the latest versions once patches become available. Additionally, conduct security audits of session management and parameter validation mechanisms within phpPgAdmin and related tools. For PostgreSQL environments, ensure that database access controls and logging are robust to detect and respond to suspicious queries or access patterns.

Description

phpPgAdmin 7.13.0 and earlier contains an incorrect access control vulnerability in sql.php at lines 68-76. The application allows unauthorized manipulation of session variables by accepting user-controlled parameters ('subject', 'server', 'database', 'queryid') without proper validation or access control checks. Attackers can exploit this to store arbitrary SQL queries in $_SESSION['sqlquery'] by manipulating these parameters, potentially leading to session poisoning, stored cross-site scripting, or unauthorized access to sensitive session data.

References

Community reviews

Loading reviews…