-
Pages
Twitter
- @modemgirl: Fuck yeah! I could totally murder one of those if it were laid in front of me. 1 hour ago
- Looks like I've got 5 invites to Gravity. Anyone want to check it out? 20 hours ago
- P.S. The most interesting part of that issue of @SPINmagazine isn't the Cobain material. It's the ads, product reviews and festival guide. 20 hours ago
- After seeing @waxpancake link up the @SPINmagazine archive earlier, I had to dig up the Kurt Cobain memorial issue: http://boogah.org/29 20 hours ago
-
Foursquare
Archives
- February 2010
- January 2010
- November 2009
- August 2009
- June 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
Just Another Magic Monday
Have you recently found yourself editing a post on your WordPress install only to find yourself facing the following prompt?
Well my friend, you’ve been hacked. Apparently this has something to do with the cross-site scripting (XSS) bug addressed with the WordPress 2.8.2 and 2.8.3 updates.
I’ve uncreatively dubbed this little baddie “The Magic Hack” and there appears to be a simple way to clear it up. As it stands, the only file that I’ve seen get affected by this is in “wp-includes/vars.php”. So if your copy of that file looks nothing like the one available over in the WordPress subversion repository, replace yours with a fresh copy, stat.
In fact, it’d probably be a better idea to upgrade your blog to the most recent version of WordPress using the extended upgrade instructions over on the WordPress Codex. So yeah, do that instead.
Oh, and if you’re still seeing that prompt after updating “wp-includes/vars.php”, let me know and I’ll update the post when I dig up some more info.
Update: Some people are seeing the hack showing up outside of “wp-includes/vars.php”. If you have SSH access to your server, you should be able to pick out the infected files rather quickly by doing a recursive grep from your site’s root directory:
This will show you just the filenames where the string “gzinflate” is found. If you want to see the code that grep finds — to provide yourself with a little context — just leave the “-l” switch off of the command.
Should you not have SSH access to the server where your copy of WordPress is installed, I suggest writing your host’s support team. Any host worth their salt wouldn’t mind running the command above and giving you the results.
And if you host your WordPress sites in a Windows based server environment — which doesn’t normally allow for commands like grep — do yourself a favor and go get a real host… ;)