Bill,

please be aware, that the core team is taking any security issue very serious.

1. the core team has been working hard to analyse the security issues (which has not been classified to be "hyper-critical" by our security experts) and was working for a sustainable solution, which will be included in DNN 4.8.3, as we do not provide patches, which might expose the vulnarability to anyone for reverse engineering. DNN 4.8.3 will be tested internally for a few days and be published asap.
2. if the "security scanner" states DotNetNuke.com as being secure, this simply exposes, that the tool is unable to guess the version running (due to a number .txt files removed) - because this is all, the tool is able to "analyse", not, if  it really has been "patched. Fixing the issue to expose version number will be another change in DNN 4.8.3.

I also suggeest to read the latest Blog posts by Shaun Walker and Joe Brinkman.

Bill:

With all due respect, you apparently have not read all posts from the Core Team members, there are multiple threads going on on this and not all have the responses from the Core Team.  If you did, you would have seen that the Core Team cannot just take the alleged patch without looking at the possible problem, understanding what the issue is, implementing the change, and test it properly.  They are actually working on it as we speak, and it may take a couple of days.  PowerDNN didn't say how long they took to find the issue and to fix it or whether it was actually exploited.  The Core Team has not actually been flaming PowerDNN, they were just clarifying at one particular point in time that they had not received communications from PowerDNN even though they were claiming they had sent the pertinent info to the DNN security address, they took their time.

Don't know if you saw the following post, that basically started the whole thing when the proverbial caca hit the fan: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/112/threadid/228802/scope/posts/threadpage/5/Default.aspx

I hope this answers your questions.

Carlos