WordPress 2.3.3 Hidden Links Injection Exploit and How To Not Let It Happen To You

A friend yesterday running the latest version of wordpress had some hidden links injected in his blog. I know he is very technical and knows what he is doing so started making me a little paranoid. I started search for WordPress 2.3.3 hidden links injection and as you can see there is a ton of people claiming to be running the latest and greatest WordPress version yet getting hidden links inserted in there posts. People are also inserting iframes. Its actually pretty effective if you think about it… How would you notice hidden links in old posts?

First I want to say I have never seen any evidence of a fresh 2.3.3 install of WordPress.

The issue most likely comes from either a previous exploitable file still existing in your WordPress install directory or from someone who has already hijacked your admin cookie. You see there were some wicked exploits in earlier versions that allowed people to hijack your admin cookie which authenticates you (keep me logged in).

So what to do…. well if you have WordPress 2.3.3 and you are getting owned regularly here is what you need to do.

1) Make a new fresh install of WordPress and copy over your must have files… like themes, plugins (MAKE SURE THEY ARE UP TO DATE) , images, wp-config.php

2) change your password right away. In case someone has a old hash of your password.

If you have been following the proper upgrade instructions (minus changing the admin pass) on the WordPress you should have been doing this the whole time… ya I know I was not either.

If you are a nerd like me you might want to use SVN which is super dope and is a better and easier way to keep up to date if you know how to use SVN. Here are the instructions for that

Anyway security wise out of the box most web servers are not going to help you find out the root of the problem. Most of these are POST requests and unless you are specifically logging them of have mod_security installed …. there is no log anywhere of any POST request to your web server other then one happened.

Thanks to wordpress developer donncha ocaoimh for answering my twitter 😉

Hope this helps anyone who is having there wordpress 2.3.3 getting owned.

About The Author

Comments 8

  1. RaiulBaztepo
  2. vetweb
  3. Bilgi Yarışması
  4. fransiska cute
  5. Cicely Swinford
  6. Galina Wiatrek