Redirect 404 to Home Page – Custom URL

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$notification_html'.

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'get_site_url'.

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$permalink'.

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$page'.

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'get_site_url'.

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$rdtcp_custom_page'.

Tested up to: 6.5 < 6.8. The "Tested up to" value in your plugin is not set to the current version of WordPress. This means your plugin will not show up in searches, as we require plugins to be compatible and documented as tested up to the most recent version of WordPress.

Incorrect Stable Tag. It's recommended not to use "Stable Tag: trunk". Your Stable Tag is meant to be the stable version of your plugin and it needs to be exactly the same with the Version in your main plugin file's header. Any mismatch can prevent users from downloading the correct plugin files from WordPress.org.

Detected usage of a possibly undefined superglobal array index: $_POST[&#039;rdtcp_redirect_type&#039;]. Use isset() or empty() to check the index exists before using it

wp_redirect() found. Using wp_safe_redirect(), along with the &quot;allowed_redirect_hosts&quot; filter if needed, can help avoid any chances of malicious redirects within code. It is also important to remember to call exit() after a redirect so that no other unwanted code is executed.