News for hackers. Stuff that matters.
Re:Tales of SugarCRM Security Horrors by wyldfire on Monday April 24, 2017 @10:21AM (#14184516)
I think we could address all of your issues if only we could design it such that something clicked the button as often as possible.

cron, maybe?

Re:Tales of SugarCRM Security Horrors by redler on Monday April 24, 2017 @05:14PM (#14188354)
Perhaps SugarCRM should create a new "Secure Enterprise Edition" of the product. The fees would be substantially higher, of course, with the proceeds used to hire overseas IT shops whose 24/7 staff would remained logged in, clicking the button repeatedly. To mitigate the privacy concerns, SugarCRM could create a special version of that administrative page with nothing except the "Remove XSS" button.
Re:Tales of SugarCRM Security Horrors by pgeorgi on Monday April 24, 2017 @02:03PM (#14186486)
or process any data in that way while it is added or read. that avoids scanning the whole table, too.