SQL injection vulnerability in wp-includes/query.php in WordPress 2.3.1 and earlier allows remote attackers to execute arbitrary SQL commands via the s parameter, when DB_CHARSET is set to (1) Big5, (2) GBK, or possibly other character set encodings that support a "\" in a multibyte character. Reproducible: Always
Feel free to cc maintainers and set a whiteboard as proposal yourself ;-)
web-apps, please advise.
No patch available and I don't see a chance at fixing it myself. Should we mask it again?
Upstream bug: http://trac.wordpress.org/ticket/5455
(In reply to comment #3) > No patch available and I don't see a chance at fixing it myself. Should we mask > it again? No need to jump to a mask if we can fix it within target delay, which is 40 days for ~X. Let's give the Wordpress folks some days.
Added 2.3.2 to the tree. All archs unstable. Removed insecure versions. webapps done here.