Get WordPress vulnerability alerts from the WPVulnerability Database API.
| Code | Message | Location | Category | |
|---|---|---|---|---|
| ERROR | WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedVariableFound | Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$wpmail". | wpvulnerability-admin.php:85:5 | Plugin Repo |
| ERROR | WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedFunctionFound | Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "wp_doing_cron". | wpvulnerability.php:137:5 | Plugin Repo |
| ERROR | WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedHooknameFound | Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "wp_doing_cron". | wpvulnerability.php:138:35 | Plugin Repo |
| WARNING | trademarked_term | The plugin name includes a restricted term. Your plugin name - "WPVulnerability" - contains the restricted term "wp" which can be used , as long as you don't change it to the full name. For example: You can use WP but not WordPress. | wpvulnerability.php | Plugin Repo |
| WARNING | trademarked_term | The plugin slug includes a restricted term. Your plugin slug - "wpvulnerability" - contains the restricted term "wp" which can be used within the plugin slug, as long as you don't use the full name in the plugin name. For example: You can use WP but not WordPress. | wpvulnerability.php | Plugin Repo |
| WARNING | trademarked_term | The plugin name includes a restricted term. Your plugin name - "WPVulnerability" - contains the restricted term "wp" which can be used , as long as you don't change it to the full name. For example: You can use WP but not WordPress. | readme.txt | Plugin Repo |
| 17.12.2025, 17:00:31 | 27s | 99 | 3 | 3 |
| 13.11.2025, 16:13:29 | 36s | 98 | 11 | 3 |