A couple months ago, Technorati announced that users of Wordpress needed to upgrade to the latest available version (now at Version 2.5). This week, Technorati announced that blogs remaining vulnerable to identified security exploits may no longer be indexed by their service.

Because of this ongoing problem, we're discontinuing processing crawls of blogs that exhibit common symptoms of being compromised. We strongly recommend upgrading your WordPress installation. Even if you haven't been afflicted by a compromise, by the time you are aware that you have been a number of negative consequences may have already occurred (for instance, flagged spam by Technorati, Google or Yahoo!) -- this has been reported by many WordPress users.

By not upgrading your software, the search engine services may block your site from being listed. I can't think of a greater incentive to update your content management software to the latest version than the threat of being delisted. This is a bold move by Technorati. I'm personally glad Technorati is taking a stand against sites hosting older versions of Wordpress with the known security holes. In my opinion, there really isn't a good reason you shouldn't be upgrading your Wordpress site to the latest version.

"I recently asked if you were ready for WordPress 2.5, but let’s go through the steps to prepare your blog for upgrading to the new version next week."

Complete Story found via Weblog Tools Collection

For those that are curious, I've started an image gallery of screenshots I've taken while playing with Drupal 6. Not much in the gallery yet, but I'll place more in their from my weekend visits with Drupal 6.

I recently upgrade a blog of mine from Wordpress 2.2 to Wordpress 2.3.  My wife and I don't post on the blog much (looking for better ideas on how to utilize the site), but it's great to keep around to test the latest and greatest Wordpress has to offer.  In my view, the most important new feature in Wordpress 2.3 is the baseline introduction of tags (also called taxonomy or even categories in other CMS applications).

"When DotNetNuke released version 4.5, we decided that the next version of Active Forums would only support DotNetNuke 4.5 and higher. Why? Because it's the best release we have seen yet and offers some of the latest technology functions that we can leverage in our products. If you haven't upgraded yet, why not?

What I find really amazing is that we have had a handful of new customers purchase Active Forums 3.7 only to find out that they are stuck on an older version of DotNetNuke. DotNetNuke 3.x hasn't seen a release since 11/30/2006 and that was marked as the final release for ASP.NET 1.1.

Let's look at some reasons you could be stuck on an older version and how to avoid them."

Complete Story

This is old news with the original announcement dated February 10, 2007 but something that slipped by me until last week.  An update to SMF, SMF 1.1.2 is available.

Simple Machines is proud to announce the release of SMF 1.1.2. Since the release of SMF 1.1 a number of bugs have been found by the community members here and this release should fix all major outstanding bugs in SMF. In addition a couple of security issues were pointed out to us which we have patched in this release. We have also fixed a number of issues with UTF-8 support - including emails being displayed incorrectly in some webmail clients.

In addition to fixes with this release we've also rewritten much of the visual verification (i.e. CAPTCHA) code to allow the admin to set the difficulty of these images as some people were having trouble reading the current images. We'd urge all users to upgrade to SMF 1.1.2 as soon as possible to take advantage of these fixes.

Complete Story

Directly from Matt Mullenweg's post at Wordpress.org:

Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately.

Longer explanation: This morning we received a note to our security mailing address about unusual and highly exploitable code in WordPress. The issue was investigated, and it appeared that the 2.1.1 download had been modified from its original code. We took the website down immediately to investigate what happened.

The complete post providing detailed information is available at Wordpress.org.