Lengthy tale brief: If you downloaded and install WordPress 2.1.1 within the previous 3-4 days, your documents might consist of a protection manipulate that was included by a biscuit, and also you ought to update every one of your documents to 2.1.2 promptly.
Longer description: Today we got a note to our protection mailing address regarding uncommon and also extremely exploitable code in WordPress. The problem was examined, and also it showed up that the 2.1.1 download had actually been customized from its initial code. We took the web site down promptly to explore what took place.
It was identified that a biscuit had actually obtained user-level accessibility to among the web servers that powers wordpress.org, and also had actually made use of that accessibility to customize the download documents. We have actually secured down that web server for more forensics, yet right now it shows up that the 2.1.1 download was the only point touched by the strike. They customized 2 documents in WP to consist of code that would certainly permit remote PHP implementation.
This is the example you hope never ever takes place, yet it did and also currently we’re taking care of it as ideal we can. Although not all downloads of 2.1.1 were impacted, we’re proclaiming the whole variation harmful and also have actually launched a new version 2.1.2 that consists of small updates and also completely confirmed documents. We are additionally taking great deals of procedures to make certain something such as this can not take place once again, not the least of which is specifically exterior confirmation of the download plan so we’ll recognize promptly if something fails for any type of factor.
Ultimately, we reset passwords for a variety of customers with SVN and also various other gain access to, so you might require to reset your password on the forums prior to you can login once again.
What You Can Do to Aid
If your blog site is running 2.1.1, please upgrade promptly and also do a complete overwrite of your old documents, particularly those in wp-includes. Have a look at your pals blog sites and also if any one of them are running 2.1.1 decrease them a note and also, if you can, lend a hand and also assist them with the upgrade.
If you are a webhosting or network manager, block accessibility to “theme.php” and also “feed.php”, and also any type of question string with “ix=” or “iz=” in it. If you’re a client at a webhosting, you might intend to send them a note to allow them understand about this launch and also the above info.
Many Thanks to Ryan, Barry, Donncha, Mark, Michael, and also Dougal for overcoming the evening to identify and also resolve this issue, and also many thanks to Ivan Fratric for reporting it to begin with.
Inquiries and also Solutions
As a result of the extremely uncommon nature of this occasion and also launch, we have actually established an e-mail address email@example.com that you can email concerns to, and also we’ll be upgrading this entrance with even more info throughout the day.
Is variation 2.0 impacted?
No downloads were changed other than 2.1.1, so if you have actually downloaded and install any type of variation of 2.0 you ought to be great.
Suppose we upgrade from SVN?
Absolutely Nothing in the Subversion database was touched, so if you update and also preserve your blog site through SVN there is no opportunity you downloaded and install the damaged launch documents.