| Package | Affected versions | Patched versions |
|---|---|---|
| wordpress | = 0.6.2= 0.6.2.1= 0.7= 0.71= 0.71-gold= 0.711= 0.72= 1.0= 1.0-platinum= 1.0.1= 1.0.1-miles= 1.0.2= 1.0.2-blakey= 1.2= 1.2-delta= 1.2-mingus= 1.2.1= 1.2.2= 1.3.1= 1.4= 1.5= 1.5-strayhorn= 1.5.1= 1.5.1.1= 1.5.1.2= 1.5.1.3= 1.5.2= 1.6= 2.0= 2.0.1= 2.0.10= 2.0.10_rc1= 2.0.10_rc2= 2.0.11= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.0.7= 2.0.8= 2.0.9= 2.1= 2.1.1= 2.1.2= 2.1.3= 2.1.3_rc1= 2.1.3_rc2= 2.2= 2.2.0= 2.2.1= 2.2.2= 2.2.3= 2.2_revision5002= 2.2_revision5003= 2.3= 2.3.1= 2.3.2= 2.3.3= 2.5= 2.5.1= 2.6= 2.6.1= 2.6.3= 2.6.5≤ 2.7.1 | |
| wordpress mu | = 1.1= 1.1.1= 1.2= 1.2.1= 1.2.2= 1.2.3= 1.2.4= 1.2.5a= 1.3= 1.3.1= 1.3.2= 1.3.3= 1.5= 1.5.1= 2.6= 2.6.1= 2.6.2= 2.6.3= 2.6.5≤ 2.7 |
wp-admin/admin.php in WordPress and WordPress MU before 2.8.1 does not require administrative authentication to access the configuration of a plugin, which allows remote attackers to specify a configuration file in the page parameter to obtain sensitive information or modify this file, as demonstrated by the (1) collapsing-archives/options.txt, (2) akismet/readme.txt, (3) related-ways-to-take-action/options.php, (4) wp-security-scan/securityscan.php, and (5) wp-ids/ids-admin.php files. NOTE: this can be leveraged for cross-site scripting (XSS) and denial of service.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free