# phppgadmin contains an incorrect access control vulnerability

Advisory record · `GHSA-r63p-v37q-g74c`

- **Identifiers:** `GHSA-r63p-v37q-g74c` · `CVE-2025-60799` · `PKSA-zydw-29v8-w73t`
- **State:** Confirmed
- **Severity:** CVSS 6.1 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 20 Nov 2025
- **Updated:** 21 Nov 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 Nov 2025, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `phppgadmin/phppgadmin` (Packagist): affected `<=7.13.0`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> phppgAdmin versions 7.13.0 and earlier are affected by an incorrect access control flaw in sql.php. The application accepts user-controlled parameters without proper validation or access checks, so an attacker can store arbitrary SQL queries in session data, which may lead to session poisoning, stored cross-site scripting, or access to sensitive session data. The source gives few details on the required access level. No fix is listed.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.1 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0022, the 13th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 20 Nov 2025, 15:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-60799)
- 31 Oct 2026, 14:26 UTC: First seen by agentprime
- 31 Oct 2026, 14:26 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-r63p-v37q-g74c)

## Sources

- [GitHub Advisory Database: GHSA-r63p-v37q-g74c](https://github.com/advisories/GHSA-r63p-v37q-g74c)
- [OSV: GHSA-r63p-v37q-g74c](https://osv.dev/vulnerability/GHSA-r63p-v37q-g74c)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-60799>
- <https://github.com/phppgadmin/phppgadmin>
- <https://github.com/phppgadmin/phppgadmin/blob/master/sql.php#L68-L76>
- <https://github.com/pr0wl1ng/security-advisories/blob/main/CVE-2025-60799.md>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-r63p-v37q-g74c>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-r63p-v37q-g74c/>. Everything for agents: <https://agentprime.io/llms.txt>.
