WordPress 2.1.1 hazardous, Update to 2.1.2 – San Francisco

WordPress 2.1.1 hazardous, 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 protection make use of that was included by a biscuit, as well as you ought to update every one of your documents to 2.1.2 instantly.

Longer description: Today we obtained a note to our safety mailing address regarding uncommon as well as very exploitable code in WordPress. The concern was explored, as well as it showed up that the 2.1.1 download had actually been customized from its initial code. We took the web site down instantly to examine what occurred.

It was established that a biscuit had actually acquired user-level accessibility to among the web servers that powers wordpress.org, as well as had actually made use of that accessibility to customize the download data. We have actually secured down that web server for additional forensics, yet currently it shows up that the 2.1.1 download was the only point touched by the assault. 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 as well as currently we’re managing it as ideal we can. Although not all downloads of 2.1.1 were influenced, we’re stating the whole variation hazardous as well as have actually launched a new version 2.1.2 that consists of small updates as well as totally validated documents. We are likewise 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 outside confirmation of the download bundle so we’ll recognize instantly if something fails for any type of factor.

Lastly, we reset passwords for a variety of customers with SVN as well as various other accessibility, so you might require to reset your password on the forums prior to you can login once again.

What You Can Do to Assist

If your blog site is running 2.1.1, please upgrade instantly as well as do a complete overwrite of your old documents, specifically those in wp-includes. Take a look at your pals blog sites as well as if any one of them are running 2.1.1 decrease them a note as well as, if you can, join in as well as aid them with the upgrade.

If you are a webhosting or network manager, block accessibility to “theme.php” as well as “feed.php”, as well as any type of question string with “ix=” or “iz=” in it. If you’re a consumer at a webhosting, you might intend to send them a note to allow them find out about this launch as well as the above info.

Many Thanks to Ryan, Barry, Donncha, Mark, Michael, as well as Dougal for resolving the evening to find out as well as resolve this trouble, as well as many thanks to Ivan Fratric for reporting it to begin with.

Inquiries as well as Solutions

As a result of the very uncommon nature of this occasion as well as launch, we have actually established an e-mail address 21securityfaq@wordpress.org that you can email inquiries to, as well as we’ll be upgrading this access with even more info throughout the day.

Is variation 2.0 influenced?

No downloads were modified 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.

What happens if we upgrade from SVN?

Absolutely Nothing in the Subversion database was touched, so if you update as well as 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 twitter
Share on linkedin
Share on pinterest
Share on print
Share on email

Recent News


Scroll to Top