News for hackers. Stuff that matters.
Re:Tales of SugarCRM Security Horrors by code_duck on Monday April 24, 2017 @11:51AM (#14185269)
That makes sense. The objection I feel here is the inconsistency - why accept the input in the first place, only to delete it with this button? An above comment suggests rules may be updated over time, which could explain their thinking.
Re:Tales of SugarCRM Security Horrors by koolba on Monday April 24, 2017 @12:19PM (#14185517)
Because they don't properly escape things everywhere (anywhere?) and the DB update button is a kludge to deal with existing messed up data breaking pages they don't know about.

It was probably less than an hours work to add that button vs. hundreds of hours to track down all the unescaped outputs.