Conditional Fields for Contact Form 7

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

All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.

Processing form data without nonce verification.

Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "add_conditional_panel".

Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$active_plugins".

Processing form data without nonce verification.

$_GET['post'] not unslashed before sanitization. Use wp_unslash() or similar

PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;

Detected usage of a non-sanitized input variable: $_GET['post']

Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "CF7CF".

Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "WPCF7_ADMIN_READ_WRITE_CAPABILITY".

Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "wpcf7_config_validator_available_error_codes".

Detected usage of a possibly undefined superglobal array index: $_POST['_wpnonce']. Check that the array index exists before using it.

Mismatched text domain. Expected 'cf7-conditional-fields' but got 'contact-form-7'.

File and folder names must not contain spaces or special characters.

Library files that are already in the WordPress core are not permitted.

The upgrade notice for "2.2.10" exceeds the limit of 300 characters.