Este plugin no se ha probado con las últimas 3 versiones mayores de WordPress. Puede que ya no tenga soporte ni lo mantenga nadie, o puede que tenga problemas de compatibilidad cuando se usa con las versiones más recientes de WordPress.

Prevent XSS Vulnerability


This plugin provides the functionality for Reflected XSS and Self-XSS.

For Reflected XSS, it checks the URL and redirects it if you enabled the Enable Blocking option and URL contains any Vulnerable code in it. It only block some parameters which are not allowed in URL and shown Block Parameters section. You can skip some of the parameters from it if you still like them to be used.

To provide more security, Prevent XSS Vulnerability also escape the HTML in the $_GET parameter which is commonly used to get parameters in PHP from the URL and print them in the HTML. This way, HTML properties will not work if anyone provided it in the URL.

There are many ways by which the plugin can be tested but it may varies for different sites according to their structure and development functionality.

Block Parameters

Prevent XSS Vulnerability block the following parameters in the URL if enabled from the Plugin Settings page.
  • Opening Round Bracket (
  • Closing Round Bracket )
  • Less than Sign <
  • Greater than Sign >
  • Opening Square Bracket [
  • Closing Square Bracket ]
  • Opening Curly Bracket {
  • Pipe or Vertical Bar |
  • Closing Curly Bracket }

You can exclude any of the pre-defined parameter(s) or include any other parameter(s) from the Plugin Settings page.

Encode Parameters

Prevent XSS Vulnerability encode the following parameters in the URL if enabled from the Plugin Settings page.
  • Exclamation Mark !
  • Double Quotation "
  • Single Quotation '
  • Opening Round Bracket (
  • Closing Round Bracket )
  • Asterisk Sign *
  • Less than Sign <
  • Greater than Sign >
  • Grave Accent «`
  • Cap Sign ^
  • Opening Square Bracket [
  • Closing Square Bracket ]
  • Opening Curly Bracket {
  • Pipe or Vertical Bar |
  • Closing Curly Bracket }

You can exclude any of the pre-defined parameter(s) to being encoded from the Plugin Settings page.

Escape HTML in `$_GET` Variable

Prevent XSS Vulnerability escape HTML  in `$_GET` variable. `$_GET` variable is mostly used to put the values in HTML from the URL. This Check is quite useful if your site using/getting anything from the URL and printing it in HTML. It secures your Search and other sections as per your site functionality.

NOTE: Make sure to check your forms after activating the plugin and if you have woocommerce site then please also check the cart and checkout process.

Bug reports

Bug reports for Prevent XSS Vulnerability are welcomed on GitHub. Please note GitHub is not a support forum, and issues that aren’t properly qualified as bugs will be closed.


  • It removes the parameters from the URL which are used in XSS Attack and redirects the user (Recommended).

  • It encodes the parameters from the URL which are used in XSS Attack.

  • It escapes the HTML from the $_GET PHP variable which is mostly used to read the data from the URL (Recommended).

  • Add the message in developer console for the user to alert about the XSS attack.

  • Show message in developer console to alert user about the Self-XSS attack. This message can be customized from the settings page.


This process defines you the steps to follow either you are installing through WordPress or Manually from FTP.

From within WordPress

  1. Visit ‘Plugins > Add New’
  2. Search for Prevent XSS Vulnerability
  3. Activate Prevent XSS Vulnerability from your Plugins page.
  4. Go to «after activation» below.


  1. Upload the prevent-xss-vulnerability folder to the /wp-content/plugins/ directory
  2. Activate Prevent XSS Vulnerability through the ‘Plugins’ menu in WordPress
  3. Go to «after activation» below.

After activation

  1. Navigate to the Prevent XSS Vulnerability page from the Admin Dashboard
  2. Make the changes as per your site functionality
  3. You’re done!


Q. Why should I install this plugin?

A. Installing this plugin is the easiest way to prevent your site from XSS Vulnerability.

Q. Does this plugin escape HTML in printing search?

A. Yes, this plugin escape HTML in $_GET variable which is mostly use to print the data from the URL to HTML. If your site is using $_GET then it is safe and the HTML will be escaped otherwise you need to check.

Q. Does this plugin has any conflict with any other plugin?

A. No, this plugin doesn’t have any conflict with any plugin.


22 de junio de 2021 1 reply
Thanks for the awesome plugin. it helps to fix the XSS attacks. But we need to add more special charter to include manually like exclude list. this helps for every one-> feature Request. keep rocking!!!... Regards, Saravanan
22 de enero de 2021
We were being harassed by our ISOs because the Acunetix scans kept coming back with HIGHs. Always XSS. We tried everything the report recommended as a remediation...nothing worked. This plugin should come bundled with WP. Or at the very least be added to the list of recommendations Acunetix suggests. Thank you for creating and sharing it.
4 de diciembre de 2019
We were directed by a security researcher to an XSS vulnerability on our site, and this plugin seems to have solved the issue. Only plugin with this functionality I was able to find. Fairly straightforward and flexible.
14 de marzo de 2018 1 reply
After running a full site scan using Acunetix and receiving hundreds of XSS alerts, this great little plugin secured the site. Bear in mind we have the free versions of Wordfence and iThemes Security installed, we incorrectly assumed that was enough... I'm not sure why this plugin isn't used, or reviewed more. Thank you!
Leer todas las 6 reseñas

Colaboradores y desarrolladores

«Prevent XSS Vulnerability» es un software de código abierto. Las siguientes personas han colaborado con este plugin.


«Prevent XSS Vulnerability» ha sido traducido a 1 idioma local. Gracias a los traductores por sus contribuciones.

Traduce «Prevent XSS Vulnerability» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

2.0.1 – Aug 19, 22

2.0.0 – Jul 14, 21

Earlier versions

  • For the changelog of earlier versions, please refer to the separate changelog.txt file.