When you include POST/GET/REQUEST/FILE calls in your plugin, it's important to sanitize, validate, and escape them. The goal here is to prevent a user from accidentally sending trash data through the system, as well as protecting them from potential security issues.
SANITIZE: Data that is input (either by a user or automatically) must be sanitized as soon as possible. This lessens the possibility of XSS vulnerabilities and MITM attacks where posted data is subverted.
VALIDATE: All data should be validated, no matter what. Even when you sanitize, remember that you don’t want someone putting in ‘dog’ when the only valid values are numbers.
ESCAPE: Data that is output must be escaped properly when it is echo'd, so it can't hijack admin screens. There are many esc_*() functions you can use to make sure you don't show people the wrong data.
To help you with this, WordPress comes with a number of sanitization and escaping functions. You can read about those here:
Clean everything, check everything, escape everything, and never trust the users to always have input sane data. After all, users come from all walks of life.
When you include POST/GET/REQUEST/FILE calls in your plugin, it's important to sanitize, validate, and escape them. The goal here is to prevent a user from accidentally sending trash data through the system, as well as protecting them from potential security issues.
SANITIZE: Data that is input (either by a user or automatically) must be sanitized as soon as possible. This lessens the possibility of XSS vulnerabilities and MITM attacks where posted data is subverted.
VALIDATE: All data should be validated, no matter what. Even when you sanitize, remember that you don’t want someone putting in ‘dog’ when the only valid values are numbers.
ESCAPE: Data that is output must be escaped properly when it is echo'd, so it can't hijack admin screens. There are many esc_*() functions you can use to make sure you don't show people the wrong data.
To help you with this, WordPress comes with a number of sanitization and escaping functions. You can read about those here:
https://developer.wordpress.org/plugins/security/securing-input/ https://developer.wordpress.org/plugins/security/securing-output/ Remember: You must use the most appropriate functions for the context. If you’re sanitizing email, use sanitize_email(), if you’re outputting HTML, use esc_html(), and so on.
An easy mantra here is this:
Sanitize early Escape Late Always Validate
Clean everything, check everything, escape everything, and never trust the users to always have input sane data. After all, users come from all walks of life.
Example(s) from your plugin:
PayViaEth-master/functions.php:281: $order_key = $_GET['key']; PayViaEth-master/admin/ajax/check_transaction_status/check_transaction_status.php:7: $cronjob=$_POST['cronjob']; PayViaEth-master/includes/_class-form.b0.php:23: return strip_tags( (string) wp_unslash( $_REQUEST[ $key ] ) ); PayViaEth-master/ethereum_payments/admin/class-ethereum_payments-list-table.php:418: $args['orderby'] = $_REQUEST['orderby']; PayViaEth-master/ethereum_payments/admin/class-ethereum_payments-list-table.php:419: $args['order'] = $_REQUEST['order'] ; PayViaEth-master/ethereum_payments/admin/views/ethereum_payments-form.php:4:
<?php echo $_GET['error'];
PayViaEth-master/ethereum_payments/admin/views/ethereum_payments-form.php:7: <?php echo $_GET['success'];