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, as well as you ought to update every one of your data to 2.1.2 right away.

Longer description: Today we got a note to our protection mailing address regarding uncommon as well as extremely exploitable code in WordPress. The concern was examined, as well as it showed up that the 2.1.1 download had actually been changed from its initial code. We took the internet site down right away to examine what took place.

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 utilized that accessibility to customize the download data. 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 data in WP to consist of code that would certainly enable remote PHP implementation.

This is the example you hope never ever occurs, however it did as well as currently we’re taking care of it as ideal we can. Although not all downloads of 2.1.1 were influenced, we’re proclaiming the whole variation unsafe as well as have actually launched a new version 2.1.2 that consists of small updates as well as completely validated data. We are additionally taking great deals of steps to make sure something such as this can not occur once again, not the least of which is specifically outside confirmation of the download plan 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 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 Aid

If your blog site is running 2.1.1, please upgrade right away as well as do a complete overwrite of your old data, particularly those in wp-includes. Have a look at your good friends blog sites as well as if any one of them are running 2.1.1 decline 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 client at a webhosting, you might intend to send them a note to allow them learn about this launch as well as the above details.

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

Inquiries as well as Responses

Due to the extremely uncommon nature of this occasion as well as launch, we have actually established an e-mail address 21securityfaq@wordpress.org that you can email concerns to, as well as we’ll be upgrading this access with even more details 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 preserve your blog site by means of SVN there is no opportunity 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