Abel Cheung has discovered a vulnerability in WordPress, which can be exploited by malicious people to conduct SQL injection attacks.
Input passed to the "s" parameter in index.php (when "exact" and "sentence" are set to "1") is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
Successful exploitation allows e.g. retrieving administrator password hashes, but requires knowledge of the database table prefix and that "DB_CHARSET" in wp-config.php is set to "GBK" or "Big5".
The vulnerability is confirmed in version 2.3.1 and reported in the previous versions down to and including 2.2.
Solution: Edit the source code to ensure that input is properly sanitised. Do not use the vulnerable character sets.
Provided and/or discovered by: Abel Cheung
Original Advisory: http://www.abelcheung.org/advisory/20071210-wordpress-charset.txt
Do you have additional information related to this advisory?
Please provide information about patches, mitigating factors, new versions, exploits, faulty patches, links, and other relevant data by posting comments to this Advisory. You can also send this
information to firstname.lastname@example.org
Subject: WordPress GBK/Big5 Character Set "s" SQL Injection
No posts yet
You must be logged in to post a comment.
Secunia Customer Login
Not a customer already?
Learn more about how our market leading Vulnerability Management solutions can help you manage risk and ensure compliance.