# CVE-2016-2560: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML into phpMyAdmin via various inputs, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 6.1 (`CVSS:3.0/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:** Yes
- **Published:** 1 Mar 2016
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-2560, GHSA-fffr-hwf6-2q7v, UBUNTU-CVE-2016-2560

## What is CVE-2016-2560?

CVE-2016-2560 is a medium-severity cross-site scripting vulnerability in Phpmyadmin Phpmyadmin, published on 1 Mar 2016. 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

Multiple cross-site scripting (XSS) vulnerabilities in phpMyAdmin 4.0.x before 4.0.10.15, 4.4.x before 4.4.15.5, and 4.5.x before 4.5.5.1 allow remote attackers to inject arbitrary web script or HTML via (1) a crafted Host HTTP header, related to libraries/Config.class.php; (2) crafted JSON data, related to file_echo.php; (3) a crafted SQL query, related to js/functions.js; (4) the initial parameter to libraries/server_privileges.lib.php in the user accounts page; or (5) the it parameter to libraries/controllers/TableSearchController.class.php in the zoom search page.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2016-2560?

It affects 1 product.


Products: Phpmyadmin Phpmyadmin.

## How do I fix CVE-2016-2560?

Upgrade to a fixed version.

## Is CVE-2016-2560 being exploited?

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

## Other vulnerabilities in Phpmyadmin Phpmyadmin

- [CVE-2008-7251](https://insights.sbomify.com/CVE-2008-7251/): Misconfiguration in n/a (critical 10.0)
- [CVE-2008-7252](https://insights.sbomify.com/CVE-2008-7252/): phpMyAdmin unsafely handles temporary files (critical 10.0)
- [CVE-2007-0203](https://insights.sbomify.com/CVE-2007-0203/): Other in n/a (critical 10.0)
- [CVE-2004-1147](https://insights.sbomify.com/CVE-2004-1147/): Command injection in n/a (critical 10.0)
- [CVE-2020-22452](https://insights.sbomify.com/CVE-2020-22452/): phpmyadmin contains SQL Injection vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-2560 and fix it if it is affected.

What it is: CVE-2016-2560 is a medium-severity cross-site scripting vulnerability in Phpmyadmin Phpmyadmin, published on 1 Mar 2016. 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-2016-2560 in the wild and no public exploit code.

Affected product: Phpmyadmin Phpmyadmin. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2016-2560/ (Markdown: https://insights.sbomify.com/CVE-2016-2560/index.md)
```

## Sources

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

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