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 data might consist of a safety and security manipulate that was included by a biscuit, and also you ought to update every one of your data to 2.1.2 promptly.

Longer description: Today we got a note to our protection mailing address concerning uncommon and also extremely exploitable code in WordPress. The concern was examined, and also it showed up that the 2.1.1 download had actually been customized from its initial code. We took the site down promptly to examine what occurred.

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 utilized that accessibility to customize the download data. We have actually secured down that web server for more forensics, however right now it shows up that the 2.1.1 download was the only point touched by the assault. They customized 2 data 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 managing it as ideal we can. Although not all downloads of 2.1.1 were impacted, 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 completely confirmed data. We are additionally taking great deals of steps to make sure something such as this can not take place once again, not the least of which is specifically outside confirmation of the download plan so we’ll recognize promptly if something fails for any kind of factor.

Lastly, we reset passwords for a variety of individuals 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 data, specifically those in wp-includes. Take a look at your buddies 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 host or network manager, block accessibility to “theme.php” and also “feed.php”, and also any kind of inquiry string with “ix=” or “iz=” in it. If you’re a consumer at a host, you might wish 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 Responses

As a result of 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 inquiries 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 kind 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 keep your blog site through SVN there is no possibility you downloaded and install the damaged launch data.

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 google
Share on twitter
Share on linkedin
Share on pinterest
Share on print
Share on email


Scroll to Top