This issue is becoming more problematic then I first thought. Thanks JackSpratts for digging deeper into the problem and not brushing it off so quickly like some of us.
If this is all true it just gives us more reasons to want version 2.0 to come out soon. Hopefully, they won't add 10 more bugs or security problems while they are at. I've been looking for more information about version 2.0 but it's just as hard to find as looking for information about this security issue.
As usually keep up the go work of informing us JS