# CVE-2025-60797: phppgadmin contains a SQL injection vulnerability

> An authenticated attacker can execute arbitrary SQL commands via the query parameter in dataexport.php, leading to database compromise.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2025
- **Updated:** 21 Nov 2025
- **Also known as:** DEBIAN-CVE-2025-60797, GHSA-927w-vq5c-8gc3, UBUNTU-CVE-2025-60797

## What is CVE-2025-60797?

CVE-2025-60797 is a medium-severity SQL injection vulnerability in n/a, published on 20 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

phpPgAdmin 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

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-60797?

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

## Is CVE-2025-60797 being exploited?

There is no known exploitation of CVE-2025-60797 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-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)
- [CVE-2025-60799](https://insights.sbomify.com/CVE-2025-60799/): phppgadmin contains an incorrect access control vulnerability (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60797 is a medium-severity SQL injection vulnerability in n/a, published on 20 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-60797 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-60797/ (Markdown: https://insights.sbomify.com/CVE-2025-60797/index.md)
```

## Sources

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

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