What is CVE-2009-3696?

CVE-2009-3696 is a medium-severity cross-site scripting (XSS) vulnerability in phpmyadmin/phpmyadmin (composer), affecting versions >= 2.11.0, < 2.11.9.6. It is fixed in 2.11.9.6, 3.2.2.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

Which versions of phpmyadmin/phpmyadmin are affected by CVE-2009-3696?

phpmyadmin/phpmyadmin (composer) versions >= 2.11.0, < 2.11.9.6 is affected.

Is there a fix for CVE-2009-3696?

Yes. CVE-2009-3696 is fixed in 2.11.9.6, 3.2.2.1. Upgrade to this version or later.

Is CVE-2009-3696 exploitable, and should I be worried?

Whether CVE-2009-3696 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2009-3696 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2009-3696 in phpmyadmin/phpmyadmin

Q: Which versions of phpmyadmin/phpmyadmin are affected by CVE-2009-3696?

phpmyadmin/phpmyadmin (composer) versions >= 2.11.0, < 2.11.9.6 is affected.

Q: Is there a fix for CVE-2009-3696?

Yes. CVE-2009-3696 is fixed in 2.11.9.6, 3.2.2.1. Upgrade to this version or later.

Q: Is CVE-2009-3696 exploitable, and should I be worried?

Whether CVE-2009-3696 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2009-3696 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2009-3696?

Upgrade: phpmyadmin/phpmyadmin to 2.11.9.6 or later, phpmyadmin/phpmyadmin to 3.2.2.1 or later.

Summary

phpMyAdmin Cross-site Scripting In MySQL Table Name

Cross-site scripting (XSS) vulnerability in phpMyAdmin 2.11.x before 2.11.9.6 and 3.x before 3.2.2.1 allows remote attackers to inject arbitrary web script or HTML via a crafted name for a MySQL table.

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Affected versions

phpmyadmin/phpmyadmin (>= 2.11.0, < 2.11.9.6) phpmyadmin/phpmyadmin (>= 3.0.0, < 3.2.2.1)

Security releases

phpmyadmin/phpmyadmin → 2.11.9.6 (composer) phpmyadmin/phpmyadmin → 3.2.2.1 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

phpmyadmin/phpmyadmin to 2.11.9.6 or later; phpmyadmin/phpmyadmin to 3.2.2.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2009-3696? CVE-2009-3696 is a medium-severity cross-site scripting (XSS) vulnerability in phpmyadmin/phpmyadmin (composer), affecting versions >= 2.11.0, < 2.11.9.6. It is fixed in 2.11.9.6, 3.2.2.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
Which versions of phpmyadmin/phpmyadmin are affected by CVE-2009-3696? phpmyadmin/phpmyadmin (composer) versions >= 2.11.0, < 2.11.9.6 is affected.
Is there a fix for CVE-2009-3696? Yes. CVE-2009-3696 is fixed in 2.11.9.6, 3.2.2.1. Upgrade to this version or later.
Is CVE-2009-3696 exploitable, and should I be worried? Whether CVE-2009-3696 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2009-3696 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2009-3696?
- Upgrade phpmyadmin/phpmyadmin to 2.11.9.6 or later
- Upgrade phpmyadmin/phpmyadmin to 3.2.2.1 or later

Other vulnerabilities in phpmyadmin/phpmyadmin

CVE-IDSeverityPackage summary

CVE-2025-24530Mediumphpmyadmin/phpmyadmin: phpMyAdmin XSS when checking tables CVE-2023-25727Mediumphpmyadmin/phpmyadmin: Cross-site Scripting vulnerability in drag-and-drop upload of phpMyAdmin CVE-2020-22452Criticalphpmyadmin/phpmyadmin: phpmyadmin contains SQL Injection vulnerability CVE-2019-12922Mediumphpmyadmin/phpmyadmin: phpMyAdmin Cross-Site Request Forgery (CSRF)CVE-2020-26934Mediumphpmyadmin/phpmyadmin: phpMyAdmin Cross-site Scripting (XSS)