Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-2561

Multiple cross-site scripting (XSS) vulnerabilities in phpMyAdmin 4.4. ...

Overview

Published
1 Mar 2016
Modified
17 Jun 2026
Medium CVE
0 Registry packages
1 OS packages
3 Linux distributions
Yes Fix available

Description

Multiple cross-site scripting (XSS) vulnerabilities in phpMyAdmin 4.4.x before 4.4.15.5 and 4.5.x before 4.5.5.1 allow remote authenticated users to inject arbitrary web script or HTML via (1) normalization.php or (2) js/normalization.js in the database normalization page, (3) templates/database/structure/sortable_header.phtml in the database structure page, or (4) the pos parameter to db_central_columns.php in the central columns page.

Source: OX vulnerability database

Severity

5.4 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Weakness: CWE-79

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 6 fixes

debian 4 releases · 1 package

fixed 4
phpmyadmin
debian fixes for CVE-2016-2561
ReleasePackageFixed in
11 phpmyadmin 4:4.5.5.1-1
12 phpmyadmin 4:4.5.5.1-1
13 phpmyadmin 4:4.5.5.1-1
14 phpmyadmin 4:4.5.5.1-1

echo 1 release · 1 package

fixed 1
phpmyadmin
echo fixes for CVE-2016-2561
ReleasePackageFixed in
phpmyadmin 4:4.5.5.1-1

openSUSE 1 release · 1 package

fixed 1
phpmyadmin
openSUSE fixes for CVE-2016-2561
ReleasePackageFixed inAdvisory
Tumbleweed phpmyadmin 4.6.5.2-1.1 openSUSE-SU-2024:10054-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.