Unfiltered HTML processing issue
-
// To filter out JS, we should use domdocument, but the problem is that sometimes the // html is intentional incomplete, which would cause issues with domdocument // See https://codereview.stackexchange.com/questions/30045/regex-to-remove-inline-javascript-from-string if ($allow_unfiltered) { // even for unfiltered: strip out javascript $res = preg_replace('#<\s*script(.*?)>(.*?)<\s*/\s*script\s*>#is', '', wp_unslash($value)); # also strip out inline javascript (onalert etc) $res = preg_replace('#\bon\w+\s*=\s*\S+(?=.*>)#', '', $res); return $res;This piece of code in _eme_kses_single cuts out the chunks form from URL-s which include on<something>=<something>, besides inline JS.
For exmaple:<a href="http://evasys.semmelweis.hu/evasys/public/online/index/index?online_php=&p=22PES&ONLINEID=47457567567567">Regisztrációs felület</a>becomes:
<a href="http://evasys.semmelweis.hu/evasys/public/online/index/index? felület</a>
Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
The topic ‘Unfiltered HTML processing issue’ is closed to new replies.