A week ago, I read about the release of WordPress 2.1.1 and 2.0.9. Since it only required a few files to be upgraded or overwritten, I immediately upgraded my WordPress installation. Now, if you were like me who upgraded to WordPress 2.1.1, please read this:
If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately.
This morning we received a note to our security mailing address about unusual and highly exploitable code in WordPress. The issue was investigated, and it appeared that the 2.1.1 download had been modified from its original code. We took the website down immediately to investigate what happened.
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.
This is the kind of thing you pray never happens, but it did and now we’re dealing with it as best we can. Although not all downloads of 2.1.1 were affected, we”re declaring the entire version dangerous and have released a new version 2.1.2 that includes minor updates and entirely verified files. We are also taking lots of measures to ensure something like this can’t happen again, not the least of which is minutely external verification of the download package so we”ll know immediately if something goes wrong for any reason.
After I read this, I immediately upgraded my installation to 2.1.2. I’m posting about this to warn those who have their blogs running WordPress 2.1.1 about the security exploit and I strongly suggest that you spend time to upgrade ASAP.