WordPress 2.3.3 Vulnerabilities?

4 Comments

Verne Ho, the owner of Creative Briefing, has e-mailed me about having some problems with his blog resulting in errors for his visitors and users. He states in the e-mail that he did some investigating and found out it might be something wrong with WordPress 2.3.3. “Upon investigation, I discovered something that might suggest a vulnerability in WordPress 2.3.3. I haven’t been able to find much information on the issue so I decided to document my own findings.” he states in the e-mail.

Has anyone else been having problems like Verne? I haven’t experienced anything yet and I’m hoping I won’t have since WordPress 2.5 is scheduled for release within the next few days.

If you have been having problems like Verne, he’s posted an article on his blog for a temporary fix to solve this. If you’re interested, check it out here.

4 thoughts on “WordPress 2.3.3 Vulnerabilities?

  1. Michael, as much as I appreciate WP Candy, I don’t like how I’m rewarded for being a subscriber, by having to click through to read the full post. It’s counter-productive.

    I usually hold back, but having to do it for a post like this is quite infuriating. But hey, I suppose you got me to give you another pageview, and a comment too.

    Just a thought my friend. I’m sure you’re aware of this plugin.

  2. Hey Armen, I didn’t know of a work around to get it to work. Thank you for bringing it to my attention, and I’m sorry for the inconveniences. I’ll work on getting that plugin working.

  3. My comment reads like I’m a bit annoyed, which I don’t like. But if it has enlightened you, and helped to change it, then I suppose it served a purpose.

    Keep up the good work!

  4. Hum, closing the WordPress diretories via a .htaccess file might help, as all
    his directories are/were accessible via the browser.
    Securing a server should be the first rule, before starting to blog with any software.

Comments are closed.