I've already emailed a number of sites asking them to update their incorrect reports, but I'm sure you know how it is in the security industry, that a single report rapidly get's copied, and rarely updated. In fact I've been through this before, when an issue was raised in a beta for the early dnn 3.x range, and it took a series of mails and nearly 4 months, to get the issue updated correctly (and this was for an issue that never existed 'in the wild' as we did not support beta's in production, nor upgrades between betas)

In this case, the issue was discovered 2 months ago, and the vendor emailed his customer list with the report, and invited them to download and install the update. I also posted a few emails and a blog post to ensure that everyone would see it, but it seems that some missed it probably through mails going to email accounts they no longer used, or being caught in spam filters.

We'll add a note to the newsletter going out later this week to again alert people to this issue, and I've added an item to my workload to look into adding support for automatically checking for security issues in 3rd party modules.

Cathal

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

OnyakTech.com is back online.  It was a very simple hack with just one file replaced.  Nothing else was damaged and no information was stolen.   Even if information had been stolen, data is encrypted and financial information does not exist (it is not stored anywhere within our network or even within our reach).

I want to clarify that OnyakTech is in no way associated with the cause of the recent hackings to DotNetNuke Portals.   OnyakTech components are and have always been safe and secure. 

---

Professional DNN Extensions, custom solutions and mobile apps since 2003.
www.OnyakTech.com

I think the people in the DNN comunity did a  great job of getting the word out without giving up too much information. It is just sad to watch site after site getting hit with this. Even worse are the sites that got compromised only because they happened to be on the same server that had the module on it.