The removeScripts plugin is doing a pretty good job, but it has these three blind spots:
<set> element that matches all of the following:
- refers to an
<a> element.
- has an
attributeName attribute that equals href or xlink:href.
- has a
to attribute that starts with javascript:.
<animate> element that matches all of the following:
- refers to an
<a> element.
- has an
attributeName attribute that equals href or xlink:href.
- matches one of the following:
- has a
from attribute that starts with javascript:.
- has a
to attribute that starts with javascript:.
- has a
values attribute that contains javascript:.
- Different capitalizations of
javascript:, like JAVASCRIPT: or JaVaScRiPt:, in the href or xlink:href attribute of an <a> element, and in the cases mentioned above.
It would be great to cover these gaps, so that the plugin does not lead people to a false sense of security. :)
Thanks!
The removeScripts plugin is doing a pretty good job, but it has these three blind spots:
<set>element that matches all of the following:<a>element.attributeNameattribute that equalshreforxlink:href.toattribute that starts withjavascript:.<animate>element that matches all of the following:<a>element.attributeNameattribute that equalshreforxlink:href.fromattribute that starts withjavascript:.toattribute that starts withjavascript:.valuesattribute that containsjavascript:.javascript:, likeJAVASCRIPT:orJaVaScRiPt:, in thehreforxlink:hrefattribute of an<a>element, and in the cases mentioned above.It would be great to cover these gaps, so that the plugin does not lead people to a false sense of security. :)
Thanks!