Forum Moderators: phranque

Message Too Old, No Replies

WordPress 2.2.1 released: fixes yet more security holes

Vital update to WordPress

         

encyclo

11:17 am on Jun 23, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Announcement here:
[wordpress.org...]
Unfortunately, 2.2.1 is not just a bug fix release. Some security issues came to light during 2.2.1 development, making 2.2.1 a required upgrade. 2.2.1 addresses the following vulnerabilities:

  • Remote shell injection in PHPMailer
  • Remote SQL injection in XML-RPC Discovered by Alexander Concha.
  • Unescaped attribute in default theme
  • That middle one appears to be a worm waiting to happen, chances are you will have your WordPress install taken over if you don't upgrade quickly and you have not removed the xml-rpc file.

    amznVibe

    11:27 am on Jun 23, 2007 (gmt 0)

    WebmasterWorld Senior Member 10+ Year Member



    Yeah in this day and age there is no purpose to have the xmlrpc.php online anyway. Delete/rename it. It's only used for trackbacks/pings which are 99% spam.

    Like many, our wordpress installs are too hacked up to be upgraded unfortunately. I've got to go research these bugs and patch manually somehow.

    encyclo

    11:58 am on Jun 23, 2007 (gmt 0)

    WebmasterWorld Senior Member 10+ Year Member



    WordPress is starting to earn a very poor reputation with regards to security. There are repeated errors of this kind, one issue in particular is that, as you can (and must) use PHP directly in the themes, there can be security issues from a whole swathe of third-party code which is not ever audited by the WordPress team. The "unescaped attribute in default theme" as mentioned above is a serious enough problem in itself, but you're not necessarily any less vulnerable if you aren't using the default theme, as your custom theme may well have been based on that original code.

    So you have the unfortunate situation that you don't know, and most likely can't easily evaluate, the quality and the security of the code in your chosen theme, and WordPress aren't going to help you.

    The phpBB project lost years of development time when repeated security errors forced them to do a complete security audit of their entire codebase. WordPress may need to go down that path too, and slow or stop development until their existing code is up to scratch. Otherwise, confidence in their product is going to be seriously undermined.