-
Website
http://mashable.com/ -
Original page
http://mashable.com/2009/09/05/wordpress-attack/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
Robert Basil
142 comments · 8 points
-
Jennifer Van Grove
149 comments · 23 points
-
r0cketman22
317 comments · 52 points
-
rajagiri4
160 comments · 2 points
-
barringtonarch
150 comments · 4 points
-
-
Popular Threads
-
Enter the Zappos Sharing Happiness $3,000 Shopping Spree Giveaway Contest
3 hours ago · 81 comments
-
Your Next Car Radio Might Be Pandora
3 hours ago · 21 comments
-
Google Launches Chrome for Mac
5 hours ago · 26 comments
-
iPhone App Offers Instant Speech-to-Text Transcription
2 hours ago · 14 comments
-
BREAKING: Google Launches Real-Time Search Results
1 day ago · 96 comments
-
Enter the Zappos Sharing Happiness $3,000 Shopping Spree Giveaway Contest
I upgraded to latest version, Good luck everyone!!
Its nasty! Good luck everyone!
I upgraded to latest wordpress
Sorry, I know that doesn't help you right now -- just a consideration for future projects.
Also - I think this may only be an exploit if you were using 2.82 or 2.83? So if you haven't updated in awhile, you may be ok?
Thanks for the head's up Mashable.
Have a great day:)
Patrick.
First line of the article...
I've been using free blogger hosting so far.
http://codex.wordpress.org/Upgrading_WordPress
As for me, I'm not vulnerable - as I always upgrade to the latest possible version of a software I use very regularly :)
I upgraded...but a bit late.
Followed the instructions on how to find the hidden user and removed him/it.
I also changed the perma-link settings.
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2357046 bytes) in [...]public_html/wp-includes/http.php on line 1331
http://wordpress.org/development/2009/08/2-8-4-...
I had a new useraccount named: iseus_1e1e1e that had admin role.. Were able to delete it though.. But I really doubt that it´s gone completly..
Going to reupload the site when I have the time for it..
This all sounds like bad reporting. Way to whip everyone into a frenzy on a nice holiday weekend, though, Mashable.
Everyone should of course always download and keep a local copy of their sites, so you can replace anything vital you might accidentally overwrite if you're manually upgrading. This is standard operating procedure. You should also set things up to have your database emailed to you on a regular basis.
If you're running a dated version of WP, be advised that your old theme may not work the way you want after upgrading and could require tweaking your PHP files. I suspect these instances will be rare, but you never know.
I second the recommendation to use the premium Thesis theme, which makes all of this so much easier. I also want to reassure everyone that WP is generally rock-solid. It pays to stay current, though. At least the developers are trying to keep up with the hackers, which is more than we can say about a lot of software apps.
(one of my sites got hacked)
Those using the custom Thesis theme should update to the latest version prior to upgrading wordpress. Make a database backup and copy your code prior to upgrading.
And then never moves again. My other sites would show that line and then zoom through the rest of the upgrade process. Any ideas?
What does it mean? Wasn't the hack completed 100%? And is my blog safe now?
Even reading some of these comments is interesting. I'm seeing things like ...it's safe, but back up just in case. That's another if in my book.
I did a full blog post that details how and why I came to rely on Typepad: http://bit.ly/wQack
Kudos to Mashable for being the first to get this out there to help.
It is not always possible to upgrade to next-available version of wordpress contributing to various reasons including custom/incompatible plugins. In case of current exploit, I recommend changing DB and FTP passwords immediately and remove write permissions from wp-config and admin folder.
http://zedomax.com/blog/2009/09/06/wordpress-di...
Hope that helps!
FYI, hackers attacked couple of my blogs last month and inserted about 3,000 spam links on average, only on older blog posts.
If you don't know and these remain for months, you will lose all your Google SEO btw, so it's sorta serious that you check it if you got hacked. Just tryin' to help. :)
richie@rwsphoto
In the scheme of things, everyone needs to ask themselves this question... "Which is worse, my plugin or theme not working, or my site getting hacked and trashed (along with my reputation by my followers)?"
I'd rather have a plugin or them that's broken, then have my followers say "Don't go to any links from his site. I did and ended up with <insert malware, virus, or other problem here>."
Have a great day:)
Patrick.
Oh wait, that's right, you didn't.
That is all. MOVE ALONG PEOPLE, nothing to see here!
I see soo many blogs running old versions of wordpress.
ppl really need to update.
Also, I noticed last week it had changed the permalink structure, but I brushed it off thinking it was something to do with Dreamhost, and just changed it back thinking nothing of it.
Is there somewhere that lists how to solve these problems? I mean, I've heard it goes right into the DB so if I upgrade the DB will still be effected.
My site is somewhere where people can register and post, but I've done it so they can't access anything in wp-admin (because it lists everybody's posts in there and I don't want them to see that) So they only have access to the write-post.php page.
A while ago I tried to update it to the latest version but it didn't want to work the way I wanted it to. But it looks like I'm going to have to upgrade.
First things first, how to fix the DB from being affected? Anyone know?
export content with the built-in XML WordPress export, uninstall and reinstall WordPress and re-import the content. It’s a nasty attack that goes all the way into the database, so exporting the database will result in exporting the hacked code too.
Non-techs like me should use pencil and paper and forget this! But... I can't. So... where is the XML Wordpress export tool? And what does it export to? and then, how do I get the hacked code out in order to put the content back in?
Oh boy am I confused!