Well, I’m glad for once that I have been too busy to keep up with my upgrade path. Recently I upgraded the site to WordPress 2.1 and soon after 2.1.1 was released. Well, it turns out that there was some nasty code that found its way into the latest release. Hence, we find ourselves at 2.1.2.

It was determined that a cracker had gained user-level access to one of the servers that powers wordpress.org, and had used that access to modify the download file. We have locked down that server for further forensics, but at this time it appears that the 2.1.1 download was the only thing touched by the attack. They modified two files in WP to include code that would allow for remote PHP execution.

Um, ok. Now I’m in a quandry. Do I trust the 2.1.2 version integrity? I have to admit the WordPress crew is a diligent bunch. Shit happens. So, if you are running a site with WordPress please upgrade to 2.1.2 ASAP. Or if you are running a version previous to 2.1.1 you’re fine.

If your blog is running 2.1.1, please upgrade immediately and do a full overwrite of your old files, especially those in wp-includes. Check out your friends blogs and if any of them are running 2.1.1 drop them a note and, if you can, pitch in and help them with the upgrade.

If you are a web host or network administrator, block access to “theme.php” and “feed.php”, and any query string with “ix=” or “iz=” in it. If you’re a customer at a web host, you may want to send them a note to let them know about this release and the above information.

Fun and games. I myself am going to hold on for a couple days until the dust settles. (read=too lazy to upgrade to 2.1.2)

Article Link

UPDATE: All upgraded.

[tags]Wordpress Security, WordPress 2.1.1, Blog Security, WordPress Vulnerability, Exploit[/tags]


  1. Oh yes, you are correct. I wasn’t very clear. I have not progressed beyond 2.1. I wasn’t kidding when I said I’m feeling lazy today 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *