CVE-2009-3696: phpMyAdmin Cross-site Scripting In MySQL Table Name

phpmyadmin/phpmyadmin Updated 02 Oct 2025

Summary

02/05/2022
Yes i
Moderate
Not published

CVE-2009-3696: phpMyAdmin Cross-site Scripting In MySQL Table Name. Affects phpmyadmin/phpmyadmin across 2 version ranges.

>= 2.11.0, < 2.11.9.6 >= 3.0.0, < 3.2.2.1

Fixed in 2.11.9.6 or 3.2.2.1, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2009-3696 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

phpMyAdmin is a popular open-source administration tool for managing MySQL databases. It provides a web-based interface that allows users to perform various database management tasks, such as creating tables, executing queries, and managing user privileges. This vulnerability affects phpMyAdmin versions 2.11.x before 2.11.9.6 and 3.x before 3.2.2.1. The vulnerability allows remote attackers to inject arbitrary web script or HTML into the application by crafting a malicious name for a MySQL table.

Vulnerability Detail

The vulnerability in phpMyAdmin arises from a lack of proper input sanitization when handling table names. By exploiting this vulnerability, an attacker can inject malicious code or HTML into the application, which will be executed when the table name is displayed or processed. This can lead to various consequences, including cross-site scripting (XSS) attacks, session hijacking, and unauthorized data access. The vulnerability has a moderate severity rating and is classified under CWE-79.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 2.11.0, < 2.11.9.6 2.11.9.6
    composer require phpmyadmin/phpmyadmin:2.11.9.6
  • >= 3.0.0, < 3.2.2.1 3.2.2.1
    composer require phpmyadmin/phpmyadmin:3.2.2.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

If upgrading to the latest version is not immediately feasible, a temporary workaround is to manually sanitize user input when creating table names. This can be done by implementing input validation and filtering techniques to remove or escape any potentially malicious characters or scripts. However, this workaround is not recommended as it may be error-prone and could introduce other security risks if not implemented correctly.

Conclusion

The phpMyAdmin vulnerability (CVE-2009-3696) allows remote attackers to inject arbitrary web script or HTML into the application by crafting a malicious name for a MySQL table. This can lead to various security risks, including cross-site scripting (XSS) attacks and unauthorized data access. It is crucial to upgrade to the latest version of phpMyAdmin and regularly update the software to mitigate this vulnerability. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for phpmyadmin/phpmyadmin →

Share this vulnerability

FAQ

phpMyAdmin is an open-source administration tool for managing MySQL databases. It provides a web-based interface for performing various database management tasks.

Versions 2.11.x before 2.11.9.6 and 3.x before 3.2.2.1 of phpMyAdmin are affected by this vulnerability.

This vulnerability allows remote attackers to inject arbitrary web script or HTML into the application, potentially leading to cross-site scripting (XSS) attacks, session hijacking, and unauthorized data access.

To fix this vulnerability, it is recommended to upgrade to the latest version of phpMyAdmin (2.11.9.6 or 3.2.2.1). Regularly updating phpMyAdmin is also important to stay protected against known vulnerabilities.

A temporary workaround is to manually sanitize user input when creating table names. However, this workaround is not recommended as it may introduce other security risks if not implemented correctly.

Related vulnerabilities

Recent vulnerabilities recorded for phpmyadmin/phpmyadmin.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 2.11.0, < 2.11.9.6 2.11.9.6
    composer require phpmyadmin/phpmyadmin:2.11.9.6
  • >= 3.0.0, < 3.2.2.1 3.2.2.1
    composer require phpmyadmin/phpmyadmin:3.2.2.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback