🛡️ CVE-2011-3592 — phpmyadmin
Description
phpMyAdmin Multiple XSS Vulnerabilities
Multiple cross-site scripting (XSS) vulnerabilities in the PMA_unInlineEditRow function in js/sql.js in phpMyAdmin 3.4.x before 3.4.5 allow remote authenticated users to inject arbitrary web script or HTML via a (1) database name, (2) table name, or (3) column name that is not properly handled after an inline-editing operation.
Weakness class
CVE-2011-3592 is classified as CWE-79: Cross-site Scripting (XSS). User-supplied data is written into a page without escaping, so attacker script runs in the browser of anyone who views it.
Affected software
CVE-2011-3592 is recorded against 1 package.
- phpmyadmin/phpmyadmin (from 3.4.0 up to 3.4.5)
Timeline and source
Published on 17 May 2022 and last revised on 15 January 2024. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Web)
bugzilla.redhat.com (Web)
github.com (Package)
www.openwall.com (Web)
www.phpmyadmin.net (Web)
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| phpmyadmin/phpmyadmin | 3.4.0 | 3.4.5 |
References
Similar Threats
- High CVE-2008-7252
- Low CVE-2012-4579
- Unknown CVE-2010-2958
- High CVE-2010-4481
- Unknown CVE-2011-0986
More CVE 2011 advisories
Browse all of CVE 2011 in the advisory index.
Free Vulnerability Check
Is your site affected by CVE-2011-3592?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2011-3592 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.