WordPress 2.1.1 unsafe, Update to 2.1.2 – San Francisco

WordPress 2.1.1 unsafe, Update to 2.1.2 – San Francisco

Lengthy tale brief: If you downloaded and install WordPress 2.1.1 within the previous 3-4 days, your documents might consist of a safety make use of that was included by a biscuit, and also you must update every one of your documents to 2.1.2 right away.

Longer description: Today we got a note to our safety and security mailing address regarding uncommon and also extremely exploitable code in WordPress. The concern was checked out, and also it showed up that the 2.1.1 download had actually been changed from its initial code. We took the web site down right away to explore what occurred.

It was established 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 change the download documents. We have actually secured down that web server for more forensics, however currently it shows up that the 2.1.1 download was the only point touched by the strike. They changed 2 documents in WP to consist of code that would certainly enable remote PHP implementation.

This is the example you hope never ever takes place, however it did and also currently we’re handling it as finest we can. Although not all downloads of 2.1.1 were influenced, we’re proclaiming the whole variation unsafe and also have actually launched a new version 2.1.2 that consists of small updates and also totally validated documents. We are likewise taking great deals of steps to make sure something similar to this can not take place once more, not the least of which is specifically outside confirmation of the download bundle so we’ll understand right away 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 more.

What You Can Do to Assist

If your blog site is running 2.1.1, please upgrade right away and also do a complete overwrite of your old documents, specifically those in wp-includes. Take 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, join in and also aid 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 learn about this launch and also the above info.

Many Thanks to Ryan, Barry, Donncha, Mark, Michael, and also Dougal for resolving the evening to identify and also resolve this issue, and also many thanks to Ivan Fratric for reporting it to begin with.

Concerns and also Solutions

Due to the extremely uncommon nature of this occasion and also launch, we have actually established an e-mail address 21securityfaq@wordpress.org 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 influenced?

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 must be great.

What happens if we upgrade from SVN?

Absolutely Nothing in the Subversion database was touched, so if you update and also keep your blog site by means of SVN there is no possibility you downloaded and install the damaged launch documents.

Cogknockers is a San Francisco WordPress Development Agency with 20+ Years Experience.  WordPress Design is at the core of our services.

Share this post

Share on facebook
Share on twitter
Share on linkedin
Share on pinterest
Share on print
Share on email

Recent News


Scroll to Top