# CVE-2025-60799: phppgadmin contains an incorrect access control vulnerability

> Attackers can manipulate session variables in phpPgAdmin to store arbitrary SQL queries, leading to session poisoning or unauthorized data access.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Nov 2025
- **Updated:** 20 Nov 2025
- **Also known as:** DEBIAN-CVE-2025-60799, GHSA-r63p-v37q-g74c, UBUNTU-CVE-2025-60799

## What is CVE-2025-60799?

CVE-2025-60799 is a medium-severity missing authorization vulnerability in n/a, published on 20 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-60799?

2 open source packages ship an affected version, including phppgadmin/phppgadmin. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `phppgadmin/phppgadmin` | Packagist | All versions to 7.13.0 | None |
| `phppgadmin/phppgadmin` | Packagist | All versions to 7.13.0 | None |

Products: Phppgadmin Project Phppgadmin.

## How do I fix CVE-2025-60799?

No fix has been published for CVE-2025-60799 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-60799 being exploited?

There is no known exploitation of CVE-2025-60799 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-40619](https://insights.sbomify.com/CVE-2023-40619/): Deserialization in n/a (critical 9.8)
- [CVE-2019-10784](https://insights.sbomify.com/CVE-2019-10784/): Cross-site request forgery in phppgadmin (critical 9.6)
- [CVE-2025-60797](https://insights.sbomify.com/CVE-2025-60797/): phppgadmin contains a SQL injection vulnerability (medium 6.5)
- [CVE-2025-60798](https://insights.sbomify.com/CVE-2025-60798/): phppgadmin contains a SQL injection vulnerability (medium 6.5)
- [CVE-2025-60796](https://insights.sbomify.com/CVE-2025-60796/): phppgadmin vulnerable to Cross-site Scripting (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-60799 and fix it if it is affected.

What it is: CVE-2025-60799 is a medium-severity missing authorization vulnerability in n/a, published on 20 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-60799 in the wild and no public exploit code.

Affected packages and fixed versions:
- phppgadmin/phppgadmin (Packagist): affected all versions up to 7.13.0; no fix listed
- phppgadmin/phppgadmin (Packagist): affected all versions up to 7.13.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-60799/ (Markdown: https://insights.sbomify.com/CVE-2025-60799/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-60799
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-60799
- OSV: https://osv.dev/vulnerability/CVE-2025-60799

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-60799/
Summaries are generated and may contain mistakes; the official description above is the record.