WordPress 2.1.1 harmful, Update to 2.1.2 – San Francisco

WordPress 2.1.1 harmful, 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 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 obtained a note to our protection mailing address concerning 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 internet site down promptly to explore what occurred.

It was figured out that a biscuit had actually acquired 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 additional forensics, however currently 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 handling it as ideal we can. Although not all downloads of 2.1.1 were influenced, we’re stating the whole variation harmful and also have actually launched a new version 2.1.2 that consists of small updates and also completely confirmed data. We are likewise taking great deals of actions to make sure something such as this can not take place once more, not the least of which is specifically outside confirmation of the download plan so we’ll understand 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 more.

What You Can Do to Assist

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. Look into your buddies blog sites and also if any one of them are running 2.1.1 decline them a note and also, if you can, lend a hand 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 client at a host, 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 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

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 inquiries 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 kind of variation of 2.0 you ought to 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 opportunity 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