If he does that then it is public. I imagine it has been reported to whmcs....what problems does it fix?
Instead of being cloak and dagger about it, post what you know and the evidence/proof to back it up. Otherwise you're just leaving everyone second guessing which does nothing to help people out.
So when someone posts an exploit they get bashed for not keeping quiet and notifying WHMCS instead. Now when someone doesn't post - also get bashed for not telling. Huh?...what problems does it fix?
Instead of being cloak and dagger about it, post what you know and the evidence/proof to back it up. Otherwise you're just leaving everyone second guessing which does nothing to help people out.
If they would bother to read the descriptions that go with the exploits he has posted they could apply fixes to code he hasn't exploited yet. Doesn't seem like they are doing this though.Hope some time just WHMCS pay localhost to make a full code audit,
and give some secure coding teaching to their devs.
The "evil" lines `eval` (haha), allowing for arbitrary code execution.What is still broken?
What does the "evil" lines do? Just changing to invalid license key or is there any other harm?
I asked what had been fixed, that's somewhat different. Why bother saying anything if you're not helping?So when someone posts an exploit they get bashed for not keeping quiet and notifying WHMCS instead. Now when someone doesn't post - also get bashed for not telling. Huh?