CVE-2011-2505 json
phpMyAdmin remote variable manipulation
published 2011-07-14 15 y ago modified 2026-06-16 4 mo ago also GHSA-vqcm-r62w-w437 , EUVD-2022-5408
- cvss
- 6.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 12.9%
- EPSS 12.9% chance of exploitation in 30 days, percentile 96%
- public exploits
- 2
- Exploit-DB
Summary
libraries/auth/swekey/swekey.auth.lib.php in the Swekey authentication feature in phpMyAdmin 3.x before 3.3.10.2 and 3.4.x before 3.4.3.1 assigns values to arbitrary parameters referenced in the query string, which allows remote attackers to modify the SESSION superglobal array via a crafted request, related to a "remote variable manipulation vulnerability."
Patch / fix
- packagist phpmyadmin/phpmyadmin 3.3.10.2, 3.4.3.1
- phpmyadmin Debian 14, Debian 13, Debian 12 4:3.4.3.1-1
debian advisories DEBIAN-CVE-2011-2505
Timeline
- First public exploit (EDB-17510)
- Published
Exploit prediction
12.88% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-17514 phpMyAdmin 3.x - Swekey Remote Code Injection webapps, 2011-07-09
- EDB-17510 phpMyAdmin3 (pma3) - Remote Code Execution webapps, 2011-07-08
- ha.xxor.se http://ha.xxor.se/2011/07/phpmyadmin-3x-multiple-remote-code.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:N/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | phpmyadmin/phpmyadmin | >=3.0, <3.3.10.2 >=3.4, <3.4.3.1 |
3.3.10.2 3.4.3.1 |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
phpmyadmin.net
/home_page/security/PMASA-2011-5.php
web, patch, vendor-advisory
-
github.com
/phpmyadmin/composer/commit/7ebd958b2bf59f96fecd5b3322bdbd0b244a7967
web
-
github.com
/phpmyadmin/phpmyadmin/commit/6e6e129f26295c83d67b74e202628a4b8bc49e54
web
-
github.com
/phpmyadmin/phpmyadmin/commit/7ebd958b2bf59f96fecd5b3322bdbd0b244a7967
web
-
exploit-db.com
/exploits/17514/
exploit
-
ha.xxor.se
/2011/07/phpmyadmin-3x-multiple-remote-code.html
web, exploit
-
mandriva.com
/security/advisories?name=MDVSA-2011:124
vendor-advisory
-
debian.org
/security/2011/dsa-2286
vendor-advisory, web
-
lists.fedoraproject.org
/pipermail/package-announce/2011-July/062719.html
vendor-advisory, web
-
secunia.com
/advisories/45139
third-party-advisory, vendor-advisory
- xxor.se /advisories/phpMyAdmin_3.x_Multiple_Remote_Code_Executions.txt
-
openwall.com
/lists/oss-security/2011/06/28/2
mailing-list, web
- typo3.org /teams/security/security-bulletins/typo3-sa-2011-008/
-
secunia.com
/advisories/45292
third-party-advisory
-
openwall.com
/lists/oss-security/2011/06/28/6
mailing-list, web
-
openwall.com
/lists/oss-security/2011/06/28/8
mailing-list, web
-
securityreason.com
/securityalert/8306
third-party-advisory, web
-
osvdb.org
/73611
vdb-entry
- phpmyadmin.git.sourceforge.net /git/gitweb.cgi?p=phpmyadmin/phpmyadmin%3Ba=commit%3Bh=7ebd958b2bf59f96fecd5b3322bdbd0b244a7967
-
securityfocus.com
/archive/1/518804/100/0/threaded
mailing-list
-
openwall.com
/lists/oss-security/2011/06/29/11
mailing-list, web
-
secunia.com
/advisories/45315
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2011-2505
advisory
-
github.com
/phpmyadmin/composer
package
-
web.archive.org
/web/20110712103138/http://www.xxor.se/advisories/phpMyAdmin_3.x_Multiple_Remote_Code_Executions.txt
web
-
web.archive.org
/web/20111116172111/http://www.securityfocus.com/archive/1/518804/100/0/threaded
web
-
web.archive.org
/web/20121105034518/http://www.mandriva.com/en/support/security/advisories?name=MDVSA-2011:124
web
-
typo3.org
/teams/security/security-bulletins/typo3-sa-2011-008
web
-
exploit-db.com
/exploits/17514
web
Sources
- CVE List CVE-2011-2505
- GitHub Advisory GHSA-vqcm-r62w-w437
- NVD CVE-2011-2505
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.