CVE-2025-60799
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 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.
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 allows unauthorized manipulation of session variables in sql.php (lines 68-76) by accepting user-controlled parameters ('subject', 'server', 'database', 'queryid') without validation. Attackers can store arbitrary SQL queries in $_SESSION['sqlquery'], enabling session poisoning, stored XSS, or unauthorized access to sensitive session data.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Locate phpPgAdmin installation and versionSearch for phpPgAdmin files on the system; check for version.php, VERSION, or similar version files in the web root. Common paths include /var/www/html/phppgadmin, /usr/share/phppgadmin, or similar. Open the version file to read the installed version number.Affected if The installed version is 7.13.0 or any version lower than 7.13.0.
-
Verify sql.php exists in the installationLocate the sql.php file within the phpPgAdmin directory structure, typically found in the root or a subdirectory like /page/ directory. Confirm the file is present and readable.Affected if The sql.php file exists in the phpPgAdmin installation.
-
Inspect vulnerable code in sql.php lines 68-76Open sql.php and examine lines 68-76 specifically. Look for code that accepts parameters ('subject', 'server', 'database', 'queryid') from user input (GET/POST requests) and assigns them directly to $_SESSION superglobal without validation or sanitization.Affected if The code directly assigns user-supplied 'subject', 'server', 'database', or 'queryid' parameters to $_SESSION variables without validation checks.
-
Confirm session variable manipulation is possibleTest if the application allows setting arbitrary session values by submitting requests with the mentioned parameters. Check if $_SESSION['sqlquery'] or other session variables can be set through user-controlled input.Affected if User-controlled parameters can modify $_SESSION['sqlquery'] or other session variables without authentication or validation.
-
Verify sql.php is accessible without authenticationAttempt to access sql.php directly via HTTP/HTTPS request without logging in to phpPgAdmin. Check if the script executes and processes parameters without requiring valid session credentials.Affected if sql.php is accessible and processes parameters without requiring authenticated session credentials.
A system is affected if it runs phpPgAdmin version 7.13.0 or earlier, has sql.php accessible, and the code in sql.php accepts and stores user-controlled parameters into session variables without validation.
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 dataImplement proper input validation and access control checks on session-related parameters in sql.php, and upgrade to a patched version once available.
- 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-60799 — 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-60799 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