CVE-2025-60797
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedphpPgAdmin 7.13.0 and earlier contains a SQL injection vulnerability in dataexport.php at line 118. The application directly executes user-supplied SQL queries from the $_REQUEST['query'] parameter without any sanitization or parameterization via $data->conn->Execute($_REQUEST['query']). An authenticated attacker can exploit this vulnerability to execute arbitrary SQL commands, potentially leading to complete database compromise, data theft, or privilege escalation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencephpPgAdmin 7.13.0 and earlier contains a SQL injection vulnerability in dataexport.php where user-supplied input from the $_REQUEST['query'] parameter is passed directly to $data->conn->Execute() without any sanitization or parameterized query implementation. An authenticated attacker can inject malicious SQL statements to execute arbitrary commands on the underlying PostgreSQL database.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 7.13.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify phpPgAdmin installation and versionLocate the phpPgAdmin installation directory and check the version.php or CHANGELOG file for the installed version numberAffected if Installed version is 7.13.0 or earlier, or version cannot be determined (assume vulnerable)
-
Verify dataexport.php existsCheck for the presence of dataexport.php in the phpPgAdmin pages directory (typically /pages/dataexport.php or /app/pages/dataexport.php)Affected if The file exists and the phpPgAdmin version is vulnerable
-
Check if authentication is enabledReview phpPgAdmin configuration (config.inc.php or config.local.php) to confirm $conf['extra_login_security'] is set to false, or check if default admin accounts are activeAffected if Authentication can be bypassed or default credentials are functional, allowing attacker access
-
Inspect dataexport.php for vulnerable code patternOpen dataexport.php and search for '$_REQUEST['query']' or '$_POST['query']' being passed directly to Execute() method without sanitization or parameter bindingAffected if The code shows direct use of user-supplied query parameter in SQL execution without prepared statements or escaping
-
Confirm query parameter handling in HTTP requestsTest if the query parameter is accepted in GET or POST requests to dataexport.php by reviewing the code's $_REQUEST usage and parameter handlingAffected if The application accepts and processes user-supplied 'query' parameter without validation
If phpPgAdmin version is 7.13.0 or earlier AND dataexport.php exists with unauthenticated or authenticated access possible, the environment is likely affected by this SQL injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace direct execution of $_REQUEST['query'] with parameterized queries using bound parameters, or implement strict input validation and whitelisting of allowed SQL commands before execution. If no patched version is available, consider disabling the dataexport functionality until a fix can be applied.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60797 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-60797 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data