Prevent XSS Vulnerability Plugin

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, this plugin 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

This plugin 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

This plugin 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

This plugin 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.

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.

Manually

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!

1. 

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

2. 

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

3. 

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

4. 

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

5. 

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

2.0.1 – Aug 19, 22

• Bug
  • Please fix Notices for use in WP_DEBUG mode

2.0.0 – Jul 14, 21

• Bug

  • Unable to execute bulk actions of WooCommerce orders when this plugin is enabled
  • Bulk actions dont work (ie bulk delete pages, images)
  • Facing conflict issue while perform bulk delete option on post

• Enhancements
  * Include other/extra parameters
  * Fixed WPCS issues

Earlier versions

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