WordPress 2.9.2 was released yesterday and in following the recent trend, it contained a security patch.
It would seem that the idiot-proofing “feature” of sending posts to the trash instead of deleting them permanently allows logged in users to see the posts.
You can read all the details over on Thomas Mackenzie’s blog but basically if you have any sensitive data in a post that you trashed or perhaps said something unflattering, you need to upgrade immediately as any registered user of your blog can view it no matter what permissions they might have.
Now, before I start in on my brief bit of commentary on this issue, please let me make something clear. I appreciate all the time and effort any and all WP devs contribute. WordPress is a platform driven by the good will of many smart coders.
WordPress Doesn’t Take Security Seriously – FACT
That being said, it has become painfully obvious that WordPress is completely inept when it comes to security. There have been countless vulnerabilities discovered of varying degrees of seriousness. This lapse probably won’t impact a ton of users negatively but it does continue the disturbing trend of WP vulnerability.
Yes, WordPress has made the upgrade process a hell of a lot faster & yes, they’ve implemented an alert system that lets users know when their installations are out of date. But instead of coming up with new and creative ways to help users stay upgraded, how about spending a healthy amount of time on security issues before each release?
WordPress 2.9 has been downloaded over 4 million times and with that many blogs depending on your platform, you’d better have a better security plan than throw it out there & patch as things are found.
How about oh, I don’t know, hiring a security expert to pound on features before they’re released? How about recruiting some of the most devious minds in PHP to try and break things when Beta testing?
If there aren’t funds currently available for this (although there’s no way for anyone other than Matt Mullenwege to know that) there are plenty of ways to raise money for the purpose of increasing security.
There are currently affiliate links for different web hosts and in the past it has been suggested that those funds go to keeping the server running. Why not toss a few more affiliate links (perhaps on the Premium Theme page) to pay for a security expert? If you don’t like that method, just put a paypal link up and ask for donations.
The point is that if WordPress were REALLY serious about security issues, there are PLENTY of ways to go about address the glaring problem. Instead, we’re treated to a round of “we’re donating our time, not enough people participate in beta testing” excuses.
Until that changes WordPress’ security will remain the joke that it is.