WordPress was “born out of a desire for an elegant, well-architectured personal publishing system built on PHP and MySQL and licensed under the GPL. It is the official successor of b2/cafelog. WordPress is fresh software, but its roots and development go back to 2001. It is a mature and stable product. We hope by focusing on user experience and web standards we can create a tool different from anything else out there.”
While testing WordPress it was discovered that WordPress supports trackbacks in different charsets when PHP’s mbstring extension is installed. This feature can be abused to bypass WordPress’s SQL parameter escaping which leads to an SQL injection vulnerability that can result in a compromise of the admin account and end in a server compromise.
Full details of the vulnerability here.
An exploit is available here.
A work-around is available if something is stopping you from upgrading. WordPress 2.0.6 has fixed this problem.
Open wp-trackback.php and comment the following lines, this will prevent anyone from changing the default charset from the ‘safe’ ones to the ‘unsafe’ ones (UTF-7 to name one):
$charset = strtoupper( trim($charset) );
It is recommended to upgrade to WordPress 2.0.6 ASAP though.
- WordPress Critical Zero-Day Vulnerability Fixed In A Hurry
- Commix – Command Injection Attack Tool
- Pinterest Bug Bounty Program Starts Paying
- WordPress 2.0.7 Follows Hot on the Tail of WordPress 2.0.6
- Serious WordPress Vulnerability/Exploit Verion 2.0.3 and Below
- Plecost – WordPress Fingerprinting Tool
Most Read in Exploits/Vulnerabilities:
- Learn to use Metasploit – Tutorials, Docs & Videos - 230,338 views
- AJAX: Is your application secure enough? - 119,500 views
- eEye Launches 0-Day Exploit Tracker - 85,224 views