Lol, instead of writing tickets, they are going to write code to prevent the user from getting hacked again. :)

That's why we pay the tax....

Bring them in......Blue lights, noisy sirens....

Serve and protect.....:eek:

How can you prove it's this hack if it's not solely responsible?????????

I have looked at the code, just out of curiosity, and until someone presents otherwise, I condem this assassination mearly a lame attempt at drama. Thats where I am leaving it.

I would like to clarify some things. I did not receive any notification from the Staff (vB.org) about potential vulnerability in this modification. The user who wrote post about hacked site, also does not provide any evidence that would confirm that this modification is flawed. The modification has not been suspended by the administration of this board and currently it is free from any vulnerabilities. I am waiting for any action, not baseless accusations.

I would not worry about it, kastak, seems like a bunch of marshmallow fluff to me. :)

Proving a security hole is quite easy, simply find where the SQL injection or code execution hole exists (bad eval, preg_replace with /e modifier etc.).
In previous cases of mods with issues the specific faulty code is reported to staff and the mod is put on hold.

Make sure you have hard proof, otherwise it is most likely that you were hacked via some other vector.

That's what I was saying, it's the users other vulnerabilities or mods like vbseo not up to date!

Great mod thanks! I'm surprised I've missed this one for so long.

Again I'm really pleased with this mod. Thank you!

However if I had to make one suggestion it would be including some kind of SPAM flood protection. Either a time limit after which subsequent edits are not reported or simply a limit to the number of notifications per user per day...