Setup individual charges for each payment method in WooCommerce.
Category Scores
Top Issues by Category
security68
maintainability19
i18n8
repo_compliance1
Issues Details
96 issues found in latest scan
Processing form data without nonce verification.
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$current_section'.
Processing form data without nonce verification.
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "wcml_raw_price_amount".
A function call to __() with texts containing placeholders was found, but was not accompanied by a "translators:" comment on the line above to clarify the meaning of the placeholders.
Detected usage of a possibly undefined superglobal array index: $_POST[$prefix . '_pay4pay_charges_fixed']. Check that the array index exists before using it.
$_POST[$prefix . '_pay4pay_item_title'] not unslashed before sanitization. Use wp_unslash() or similar
strip_tags() is discouraged. Use the more comprehensive wp_strip_all_tags() instead.
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Resource version not set in call to wp_enqueue_script(). This means new versions of the script may not always be loaded due to browser caching.
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$current_section".
Detected usage of a non-sanitized input variable: $_POST[$prefix . '_pay4pay_tax_class']
In footer ($in_footer) is not set explicitly wp_enqueue_script; It is recommended to load scripts in the footer. Please set this value to `true` to load it in the footer, or explicitly `false` if it should be loaded in the header.
Mismatched text domain. Expected 'woocommerce-pay-for-payment' but got 'pay4pay'.
Multiple placeholders in translatable strings should be ordered. Expected "%1$s, %2$s, %3$s, %4$s", but got "%s, %s, %s, %s" in 'To fix the issue, contact the plugin author either on %sGithub%s or %sWordPress.org%s and provide following information:'.
Tested up to: 6.9 < 7.0. 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.
The plugin slug includes a restricted term. Your plugin slug - "woocommerce-pay-for-payment" - contains the restricted term "woocommerce" which cannot be used within in your plugin slug, unless your plugin slug contains one of the allowed patterns: "for woocommerce", "with woocommerce", "using woocommerce", or "and woocommerce". The term must still not appear anywhere else in your plugin slug.
| Code | Type | Message | Count |
|---|---|---|---|
| WordPress.Security.NonceVerification.Missing | WARNING | Processing form data without nonce verification. | 37 |
| WordPress.Security.EscapeOutput.OutputNotEscaped | ERROR | All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$current_section'. | 10 |
| WordPress.Security.NonceVerification.Recommended | WARNING | Processing form data without nonce verification. | 8 |
| WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedHooknameFound | WARNING | Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "wcml_raw_price_amount". | 7 |
| WordPress.WP.I18n.MissingTranslatorsComment | ERROR | A function call to __() with texts containing placeholders was found, but was not accompanied by a "translators:" comment on the line above to clarify the meaning of the placeholders. | 6 |
| WordPress.Security.ValidatedSanitizedInput.InputNotValidated | WARNING | Detected usage of a possibly undefined superglobal array index: $_POST[$prefix . '_pay4pay_charges_fixed']. Check that the array index exists before using it. | 5 |
| WordPress.Security.ValidatedSanitizedInput.MissingUnslash | WARNING | $_POST[$prefix . '_pay4pay_item_title'] not unslashed before sanitization. Use wp_unslash() or similar | 4 |
| WordPress.WP.AlternativeFunctions.strip_tags_strip_tags | ERROR | strip_tags() is discouraged. Use the more comprehensive wp_strip_all_tags() instead. | 4 |
| WordPress.Security.EscapeOutput.UnsafePrintingFunction | ERROR | All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'. | 3 |
| missing_direct_file_access_protection | ERROR | PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit; | 3 |
| WordPress.WP.EnqueuedResourceParameters.MissingVersion | WARNING | Resource version not set in call to wp_enqueue_script(). This means new versions of the script may not always be loaded due to browser caching. | 2 |
| WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedVariableFound | WARNING | Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$current_section". | 1 |
| WordPress.Security.ValidatedSanitizedInput.InputNotSanitized | WARNING | Detected usage of a non-sanitized input variable: $_POST[$prefix . '_pay4pay_tax_class'] | 1 |
| WordPress.WP.EnqueuedResourceParameters.NotInFooter | WARNING | In footer ($in_footer) is not set explicitly wp_enqueue_script; It is recommended to load scripts in the footer. Please set this value to `true` to load it in the footer, or explicitly `false` if it should be loaded in the header. | 1 |
| WordPress.WP.I18n.TextDomainMismatch | ERROR | Mismatched text domain. Expected 'woocommerce-pay-for-payment' but got 'pay4pay'. | 1 |
| WordPress.WP.I18n.UnorderedPlaceholdersText | ERROR | Multiple placeholders in translatable strings should be ordered. Expected "%1$s, %2$s, %3$s, %4$s", but got "%s, %s, %s, %s" in 'To fix the issue, contact the plugin author either on %sGithub%s or %sWordPress.org%s and provide following information:'. | 1 |
| outdated_tested_upto_header | ERROR | Tested up to: 6.9 < 7.0. 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. | 1 |
| trademarked_term | WARNING | The plugin slug includes a restricted term. Your plugin slug - "woocommerce-pay-for-payment" - contains the restricted term "woocommerce" which cannot be used within in your plugin slug, unless your plugin slug contains one of the allowed patterns: "for woocommerce", "with woocommerce", "using woocommerce", or "and woocommerce". The term must still not appear anywhere else in your plugin slug. | 1 |
Latest Snapshot
Findings
96
Errors
29
Warnings
67
Score History
First score snapshot
First scan completed
v2.2.2 · Plugin Check 2.0.0 · Model 2026.06-mvp-static-v2
v2.2.2
41
Latest
- Findings
- 96
- Errors
- 29
- Warnings
- 67
- Plugin Check
- 2.0.0
- Model
- 2026.06-mvp-static-v2
| Scan | Score | Findings | Errors | Warnings | Plugin | Plugin Check | Model |
|---|---|---|---|---|---|---|---|
| Latest | 41 | 96 | 29 | 67 | v2.2.2 | 2.0.0 | 2026.06-mvp-static-v2 |