So do we know just exactly what the exploit is?

Simply in case this does not come back. So some of the more capable members can devise a fix for themselves and maybe share...

no

if the exploit source know by public, many site that already using this script may be attacked

The exploit was fixed in 1.2.6 so if you updated to that you are fine. If you are using 1.2.5 the exploit remains.

EDIT - Looks like efc9 has posted this mod over on vbhackers.com, so go there to get an updated version. Looks like he'll be continuing development over there.

I'm not sure if this is allowed, so I'll post this and if either efc9 or the moderator tells me that it's not appropriate, then I'll remove this post, but I have the 1.2.6 version (the version with the exploit fix) and I'll email it to anyone who needs it, just PM me. Please, if you PM me, only do it once and I'll send it as soon as I see the PM, like right now i'm posting this and going to bed, so I won't be sending any emails tonight.

To efc9, your mod is great, I hope that you continue work on it and post it here!

Strange that he would remove this, glad i downloaded before it was taken down. Hopefully he takes this commercial or makes it better.

Hey author, don't let others get you down if that was the case. You have a very good mod here, and im sure there is more to come. vb.org is a very useful tool for coders to get their name out so don't let one or even a few bad comments or actions ruin it for you, and us. I think your install count proves the point im trying to make.

I absolutely agree with this post!

Jacquii.

Get used to getting 1 star when releasing a modification around here, in case that was the problem. :/

Whew, good thing I upgraded when he updated it this morning. I hope whatever the issues are they get resolved and we see efc9 back soon. He was giving this modification stellar support and there are many other mod authors who have some major chips on their shoulders who could learn a thing or two from efc9.

This wasn't a case where the author had a melt down over one review.

This was a case where the author was treated rudely by the VB.org staff and decided to take their works somewhere else.

Watch for 1.3 to crop up over at vbhackers.com when it's finished.

I think we need to be careful when dealing with the coders that are producing items for vb.org and the vbulletin community. I am pretty sure most coders don't intentionally code-in an exploit. They give freely and get little in return. We need to rememebr that.