Wordpress 2.1.2 Update

[The.Clinton]

Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately.

Longer explanation: This morning we received a note to our security mailing address about unusual and highly exploitable code in WordPress. The issue was investigated, and it appeared that the 2.1.1 download had been modified from its original code. We took the website down immediately to investigate what happened.

It was determined that a cracker had gained user-level access to one of the servers that powers wordpress.org, and had used that access to modify the download file. We have locked down that server for further forensics, but at this time it appears that the 2.1.1 download was the only thing touched by the attack. They modified two files in WP to include code that would allow for remote PHP execution.

This is the kind of thing you pray never happens, but it did and now we?re dealing with it as best we can. Although not all downloads of 2.1.1 were affected, we?re declaring the entire version dangerous and have released a new version 2.1.2 that includes minor updates and entirely verified files. We are also taking lots of measures to ensure something like this can?t happen again, not the least of which is minutely external verification of the download package so we?ll know immediately if something goes wrong for any reason.

Finally, we reset passwords for a number of users with SVN and other access, so you may need to reset your password on the forums before you can login What You Can Do to HelpHelp

If your blog is running 2.1.1, please upgrade immediately and do a full overwrite of your old files, especially those in wp-includes. Check out your friends blogs and if any of them are running 2.1.1 drop them a note and, if you can, pitch in and help them with the upgrade.

If you are a web host or network administrator, block access to ?theme.php? and ?feed.php?, and any query string with ?ix=? or ?iz=? in it. If you?re a customer at a web host, you may want to send them a note to let them know about this release and the above information.

Thanks to Ryan, Barry, Donncha, Mark, Michael, and Dougal for working through the night to figure out and address this problem, and thanks to Ivan Fratric for reporting it in the first place.

Questions and Answers

Because of the highly unusual nature of this event and release, we?ve set up an email address [email protected] that you can email questions to, and we?ll be updating this entry with more infIs version 2.0 affected?b>Is version 2.0 affected?

No downloads were altered except 2.1.1, so if you?ve downloaded any versWhat if we update from SVN?>What if we update from SVN?

Nothing in the Subversion repository was touched, so if you upgrade and maintain your blog via SVN there is no chance you downloaded the corrupted release file.

News source: Source

Download: Download

Edited March 2, 2007 by DeanClinton

[Rappy Veteran]

Interesting...I didn't get the 2.1.1 in the end might just get this instead :)

[Veedems Veteran]

Thanks. I upgraded just to be safe.

[DJLunacy]

My procrastination finally pays off nice.

[Chad.C]

Wowzer..

Thanks for the news.. Updating now.

[null_]

I noticed this earlier in my dashboard and updated immediately. Thanks for posting this.

[Long]

My blog was changing to the default theme every once in a while after upgrading to 2.1.1. I wonder if someone was exploiting it.

[null_]

My blog was changing to the default theme every once in a while after upgrading to 2.1.1. I wonder if someone was exploiting it.

I noticed this happening before with 2.1 itself. Weird issue to be honest.

[Jase]

"Autoupdate Plugin"... Anyone..... Anyone? :cry:

[Futurix]

Jase, it will never work reliably :no: (there are too many web servers, PHP versions, etc).

[Jase]

but all the time with updates.. Download Zip, Unzip, Open FTP app, send files.. run update... cant they incorporate it into one little plugin?

[soothsayer]

but all the time with updates.. Download Zip, Unzip, Open FTP app, send files.. run update... cant they incorporate it into one little plugin?

It'll happen eventually. It's one of the popular ideas on their website.

http://wordpress.org/extend/ideas/

[Smigit]

damn it i wasnt going to upgrade too. I may as well again to be safe now. grr.

[Echilon]

I read about this and updated with Winmerge. Whoever added the extra bits of code really knew what they were doing.

[Xtreme $niper]

Bah sorry if this is kinda off topic, but I'd assume it would be a fairly short answer... I haven't really learned how WordPress is actually set up too much, but I'm afraid to update mine mainly because I fear that the files that it requires to overwrite in order to perform the update will overwrite a file from my template design... I haven't actually gotten around to doing this yet to find out if it will happen, but can anyone tell me if my template will be safe when I do an update? Or do I have to back up certain files and restore them after the update?

[Veedems Veteran]

Custom templates aren't touched during the update. Only core files and default themes are included in the download.

[Xtreme $niper]

Custom templates aren't touched during the update. Only core files and default themes are included in the download.

Oh awesome, I guess I have no more excuses to give it a try. Not like my blog has much on it at this point. I could just back everything up and restore it if something goes wrong.

Thanks.

[Neil]

Oh awesome, I guess I have no more excuses to give it a try. Not like my blog has much on it at this point. I could just back everything up and restore it if something goes wrong.

Thanks.

As long as you don't overwrite the wp-content folder - this would mean that you would remove everything inside and start clean, that is all.

[chrisgeleven]

What you should backup before doing a WordPress upgrade:

wp-config.php (this has all of your database connection stuff)

\wp-content\ (your plugins and themes)

What I typically do is delete every file except the wp-content folder and wp-config.php, then upload the new version. Afterwards, I go into my \wp-content\plugins folder and make sure the Akismet plugin is the latest.

[The.Clinton]

What you should backup before doing a WordPress upgrade:

wp-config.php (this has all of your database connection stuff)

\wp-content\ (your plugins and themes)

What I typically do is delete every file except the wp-content folder and wp-config.php, then upload the new version. Afterwards, I go into my \wp-content\plugins folder and make sure the Akismet plugin is the latest.

Thats the same way I do it