|
WordPress GBK/Big5 Character Set "s" SQL Injection
|
|
Secunia Advisory:
|
SA28005
|
|
|
Release Date:
|
2007-12-11
|
|
Last Update:
|
2007-12-14
|
|
Popularity:
|
5,904 views
|
|
|
Critical:
|
Less critical
|
|
Impact:
|
Manipulation of data
Exposure of sensitive information
|
|
Where:
|
From remote
|
|
Solution Status:
|
Unpatched
|
|
| Software: | WordPress 2.x
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities 
|
|
| CVE reference: | CVE-2007-6318
|
|
Description:
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
Changelog:
2007-12-14: Added CVE reference.
Original Advisory:
http://www.abelcheung.org/advisory/20071210-wordpress-charset.txt
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
