For those of you not aware... http://blog.whmcs.com/?t=80298 == Security Issue Information == These changes resolve security issues identified by public disclosure. The follow security issues have been addressed within the latest patches: - Missing Cross Site Request Forgery Token checks for certain operations related to Product Bundles and Product Configuration - SQL Injection viable due to improper validation of expected numeric data - Enforce privilege boundaries for particular ticket actions == Important Fix Information == These changes also include important functional fixes that were produced from previous security patches: - SQL error in getting ticket departments (5.1 only) - Mass mail client filter excluding users set to default language - Admin clients list displaying multiple instances of the same record in certain conditions - Prevent user input from manipulating IP Ban logic (5.2 only)
There have been a lot of updates in the last month. I think it's time they review their script, thoroughly.
Yep, time for a nice external audit like SolusVM did. The things they are missing is just basic PHP too, which is scary.
While I definitely think that a nice external security audit would be great for WHMCS, I also think it is to their credit how quickly they have responded to these public exploits -- AKA within a day. That shows (to me at least) that they are committed to standing behind their product.
The last vulnerability was actually something WHMCS found on their own. The vulnerability was not reported or publicly released by localhost like the other exploits. So that tells you they are already viewing the code and working to make it better. I hope lol.
That actually isn't true. The latest one was released publically. Not sure who released it, but we knew about the exploit over a day before WHMCS released the patch.