WPVulnerability
| 开发者 |
closetechnology
davidperez javiercasares lbonomo alexclassroom |
|---|---|
| 更新时间 | 2026年7月9日 14:33 |
| PHP版本: | 7.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-3.0-or-later |
| 版权网址: | 版权信息 |
标签
下载
5.0.1
4.3.0
2.0.3
4.0.3
2.1.0
3.3.3
4.0.2
5.1.1
1.1
1.3.2
2.0.2
2.0.4
1.0.1
1.2.0
1.3.3
2.0.0
2.0.1
0.1
1.2.2
2.2.1
3.0.1
2.2.0
3.0.2
3.1.0
4.0.0
3.1.2
3.2.0
1.2.4
3.0.0
3.1.1
3.2.2
3.3.0
1.0
3.3.1
3.3.2
4.0.1
4.0.4
4.1.0
4.1.1
4.2.0
4.2.1
1.2.1
1.3.0
1.3.1
3.4.0
4.2.1.1
0.2
3.3.4
4.3.1
4.3.2
1.2.3
3.3.5
3.4.1
5.0.0
详情介绍:
This plugin integrates with the WPVulnerability API to provide real-time vulnerability assessments for your WordPress core, plugins, themes, PHP version, Apache HTTPD, nginx, MariaDB, MySQL, ImageMagick, curl, memcached, Redis, and SQLite.
It delivers detailed reports directly within your WordPress dashboard, helping you stay aware of potential security risks. Configure the plugin to send periodic notifications about your site's security status, ensuring you remain informed without being overwhelmed. Designed for ease of use, it supports proactive security measures without storing or retrieving any personal data from your site.
Data reliability
The information provided by the information database comes from different sources that have been reviewed by third parties. There is no liability of any kind for the information. Act at your own risk.
安装:
Automatic download
Visit the plugin section in your WordPress, search for [wpvulnerability]; download and install the plugin.
Manual download
Extract the contents of the ZIP and upload the contents to the
/wp-content/plugins/wpvulnerability/ directory. Once uploaded, it will appear in your plugin list.屏幕截图:
常见问题:
Where does the vulnerability information come from?
The origin is in the WPVulnerability.com API. The vulnerabilities that appear in this API come from different sources, such as CVEs.
Is data from my site sent anywhere?
No. Never. Your privacy is very important to us. We do not commercialize with your data.
What vulnerabilities will I find?
Vulnerabilities in WordPress Core, Plugins, Themes, PHP, Apache HTTPD, nginx, MariaDB, MySQL, ImageMagick, curl, memcached, Redis, and SQLite are documented.
What do I do if my site has a vulnerability?
First of all, peace of mind. Investigate what the vulnerability is and, above all, check that you have the latest version of the compromised element. We actively recommend that you keep all your WordPress and its plugins up to date. Contact your hosting provider to patch non-WordPress vulnerabilities (like web server, databases, and other software).
更新日志:
[5.1.1] - 2026-07-09
Fixed
- Site Health: the memcached, Redis, and SQLite vulnerability tests always returned "Invalid software type" because those components were missing from the software list. They now run correctly.
- "Send test email" failed when no email recipients were configured: the forced-test path added the admin email but the send gate used a flag computed before the override. The test email now sends.
- "Run notification now" reported failure when only webhook channels (Slack/Teams/Discord/Telegram) were enabled and email was disabled. The notification result now reflects whether any channel delivered successfully.
- Weekly notification cron events were never auto-scheduled, because the
weeklycron schedule was registered only atinitwhile the on-load scheduling runs earlier. The weekly/daily schedule registration moved to the always-loaded scheduler so weekly notifications schedule correctly. - Deactivation deleted the per-component analysis settings (
wpvulnerability-analyze), so deactivating and reactivating reset which components were hidden. Analysis settings are now preserved on deactivation (only uninstall removes them). - The debug "Cron Status" panel always showed the notification event as "not scheduled" because it checked the wrong hook name (
wpvulnerability_send_notificationinstead ofwpvulnerability_notification). - The debug "last run" timestamp was always empty because it read a
wpvulnerability-logsoption that is never written; it now reads the most recent API log entry. - Redis detection called
close()twice on the success path (once in thetryblock, once infinally); the redundant close was removed. - The single-site vulnerable-themes count was hardcoded to
0instead of reading the stored option.
- Single-site email recipient sanitization now uses
is_email()for strict validation, matching the multisite behaviour. - Removed a redundant nonce field from the single-site "Reset Plugin" form (the form only submits the full-reset action).
- Removed dead code: the unused
wpvulnerability_sanitize_messagescallback and its setting registration, and an unused$tools_actionvariable in the multisite admin.
wpvulnerability_validate_shell_command()now uses exactin_array()match instead ofstripos()substring matching for the shell-command allowlist (defense-in-depth).wpvulnerability_detect_php(),wpvulnerability_detect_curl(), andwpvulnerability_detect_webserver()now route throughwpvulnerability_safe_shell_exec(), so every software-detection shell call is validated and recorded in the Shell Execution Audit Log. Previously these calledshell_exec()directly, bypassing the wrapper and the audit log. As a side effect this also fixes nginx/angie version detection:escapeshellcmd()was escaping the2>&1redirect, so stderr (where nginx prints its version) was never captured.
- Multisite uninstall fatal error:
Uncaught Error: Undefined constant "WPVULNERABILITY_PLUGIN_BASE"when "Delete all plugin data on uninstall" was enabled.uninstall.phpnow defines the constant before loadingwpvulnerability-run.php. WPVULNERABILITY_HIDE_*constants now stopshell_execdetection for hidden components during scheduled scans and in the admin "Software Detection Methods" panel. Previously they only hid the results from the UI, so the audit log kept filling with "command not found" entries for components the administrator had explicitly deactivated.wpvulnerability_detect_webserver()no longer shell-probes a hidden web server via the sibling path:WPVULNERABILITY_HIDE_NGINXandWPVULNERABILITY_HIDE_APACHEnow fully isolate the hidden server.- Multisite cron requests on non-main subsites no longer load all plugin module files. No WPVulnerability cron events are scheduled on subsites, so the extra loading was wasted work.
- LiteSpeed / OpenLiteSpeed / Caddy shell detection in the WP_DEBUG diagnostic panel now works: the commands no longer use
2>/dev/null(which the shell-command validator rejected),caddywas added to the allowlist, andwhichoutput is validated as a real path so "command not found" messages are not mistaken for a detection.
Network: trueadded to the plugin header to declare network-aware multisite behaviour.- Removed the unused
$plugin_statusparameter fromwpvulnerability_plugin_info_after(); the PHPCS suite now passes with zero warnings. - Multisite network dashboard: the "Site Health" footer link pointed to
wp-admin/network/site-health.php, which does not exist (Site Health is a per-site screen). It now links to the main site'swp-admin/site-health.php.
wp_cache_flush()removed from the plugin/theme update hook and the plugin reset routine. The function was wiping the entire Object Cache (Redis, Memcached, APCu) on every update, causing CPU spikes on high-traffic sites. The targeted transient cleanup that already runs before it is sufficient.
- Vulnerability detail panels fully redesigned: Bootstrap-inspired score/severity badge, source attribution pills (hostname extracted from URL), and a structured "References:" row on the same line as the pills.
- CVSS priority order: CVSS 4 > CVSS 3 > CVSS 2 > legacy CVSS. The highest available score and severity are always shown.
ssvc.exploitationfield displayed:poc→ "⚡ Public exploit" badge;active→ included in the "Actively exploited" KEV label.ssvc.automatable: yes→ "⚙ Automatable" badge alongside KEV/PoC.ssvc.kev_date→ date appended to the "Actively exploited" label (e.g. "⚠ Actively exploited · 2024-03-15").epssfield → "EPSS X.X%" badge on the same line as the CVSS score badge.- CVE description (
source[].description) now displayed for all vulnerability types: plugins, themes, core, and server software. Language prefix (e.g.[en-US]) stripped automatically. - CWE name and description displayed in server software vulnerability details (was missing).
- Core vulnerabilities on
update-core.phpnow rendered with the same badges, description, and pills as plugin/theme rows (replaces the old plain table). - Theme details modal (single-site): vulnerability section injected after the Tags field using the
wp_prepare_themes_for_jsfilter and a JS template patch. Shows the same version range + badge + description + references layout as the plugin rows. - Version range display: leading
-or*stripped when there is no lower bound (e.g.- < 1.3.28→< 1.3.28). - Helper functions added to
wpvulnerability-process.php:wpvulnerability_source_css_slug(),wpvulnerability_render_source_pills(),wpvulnerability_render_score_badge(),wpvulnerability_clean_version_range(),wpvulnerability_get_source_description(). - Helper functions added to
wpvulnerability-themes.php:wpvulnerability_theme_modal_html(),wpvulnerability_filter_prepare_themes_for_js(),wpvulnerability_theme_modal_template_patch(). - KEV badge displayed in vulnerability details when the CVE is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog (
impact.ssvc.kevfor plugins/themes/core;impact.kevfor server software). - Vulnerability severity now uses the full-word value from
cvss3.severity("critical","high","medium","low") when available, falling back to the legacy single-charactercvss.severitycode. - Publication date shown next to each source link in vulnerability details (
source[].datefield from the API). - Server software lifecycle status (Supported / End of Life + EOL date) in vulnerability details and dashboard grid (
data.status,data.date_endfields from the API). - EOL badge in the dashboard software grid (PHP, Apache, nginx, MariaDB, MySQL, ImageMagick, curl, memcached, Redis, SQLite) when the detected version has reached end-of-life.
- REST API: all vulnerability endpoints now expose
uuid,kev(boolean),ssvcblock, andseverityfromcvss3. Source entries include adatefield. - About tab: new Intelligence Sources table showing per-source vulnerability counts (CVE, EUVD, JVN, Patchstack, WPScan, Wordfence) broken down by Core / Plugins / Themes.
wpvulnerability-adminms.php: config form handler now requiresmanage_network_optionscapability (viacurrent_user_can()) in addition to the nonce check. Previously a user with a valid nonce could update plugin options without the required capability.- WP-CLI: all vulnerability commands (
core,plugins,themes, and all software components) and all config commands (hide,email,cache,log-retention,period) now requiremanage_options/manage_network_options. Commands abort with a clear error and--user=<admin_login>hint if the check fails. - REST API permission check now passes strict mode (
true) tobase64_decode()when parsing the HTTP Basic Authorization header. A malformed or padding-stripped token is immediately rejected instead of decoding unpredictable bytes. - Debug web server detection (LiteSpeed, OpenLiteSpeed, Caddy) now routes through the
wpvulnerability_safe_shell_exec()wrapper, ensuringWPVULNERABILITY_DISABLE_SHELL_EXEC, security mode, command whitelist, and audit logging are respected even whenWP_DEBUGis enabled. - Page render callbacks (
wpvulnerability_create_admin_page,wpvulnerability_admin_dashboard_content) now include explicitcurrent_user_can()/wp_die()guards as defense-in-depth, per the WordPress Plugin Handbook.
- Forced test email on a fresh install (no email address configured yet) no longer produces an
E_WARNINGon PHP 7.x or aTypeErroron PHP 8.x. determine_locale()call is now guarded byfunction_exists()instead ofversion_compare(), which is more forward-compatible and correctly recognised by static analysis.preg_replace()return values in the HTML-to-plain-text converter are now handled safely whennullis returned on error.DOMDocument::$documentElementnull check added in the HTML-to-plain-text converter.- JSON-encoded vulnerability count options are validated as strings before
json_decode()throughout the codebase. cron_schedulescallbacks now usedid_action('init')guard before__(), eliminating the textdomain-too-early notice introduced in WordPress 6.7.- WP-CLI vulnerability commands now display a clear success message when no vulnerabilities are found, instead of an empty table.
- WP-CLI
config period monthlynow returns a proper error. Valid periods:daily,weekly,never. uninstall.phpcreated. Plugin data is preserved by default; a new "Delete all plugin data on uninstall" checkbox in the Tools tab allows opting in to full removal.- Large vulnerability data options are now stored with
autoload=false, preventing unnecessary loading of JSON blobs on every WordPress request.
- Minimum required PHP version raised from 5.6 to 7.0. The null coalescing operator (
??) used throughout for improved type safety requires PHP 7.0. PHP 5.6 reached end-of-life in December 2018. - Minimum required WordPress version raised from 4.7 to 5.6, enabling full use of Application Passwords,
wp_timezone(),wp_date(), anddetermine_locale()without version guards. wpvulnerability_get_cron_snapshot()now uses only public WordPress Cron API functions (wp_next_scheduled(),wp_get_schedule());_get_cron_array()(private WP API) removed.
- PHPStan level 9: 0 errors across all 18 PHP files; 1,092 pre-existing type errors resolved; baseline is now empty.
- Added dev tooling:
composer.json,phpstan.neon(level 9),phpcs.xml,phpunit.xml.dist,bin/deploy.sh,docs/. - Added 18 PHPUnit plugin header tests.
- WordPress: 5.6 - 7.1
- PHP: 7.0 - 8.5
- WP-CLI: 2.3.0 - 2.12.0
- PHP Coding Standards: 3.13.5
- WordPress Coding Standards: 3.3.0
- PHPStan: 2.1.55 (level 9, 0 errors)
- PHPUnit: 9.6.34 (18 tests)
- Plugin Check (PCP): 1.8.0
- Notification scheduling no longer rewrites the
cronrow inwp_optionson every WordPress request. The boot-time call now verifies the current schedule withwp_get_schedule()and only clears or reschedules thewpvulnerability_notificationevent when the desired period actually differs from the currently scheduled one. This eliminates 1-2 unnecessaryUPDATE wp_optionsqueries per page load, removing lock contention under concurrent load and the corresponding entries from the MariaDB/MySQL slow query log.
wpvulnerability_schedule_notification_event()gained an optional$forceparameter (defaulttrue, backwards compatible). The boot-time invocation passesfalseto opt into the idempotent path; all other callers (admin save handlers, WP-CLI config command, update flow, repair helpers) keep the default and continue forcing a reschedule so that changes to hour/minute/day still update the next-run timestamp.
- WordPress: 4.7 - 6.9
- PHP: 5.6 - 8.5
- WP-CLI: 2.3.0 - 2.11.0
- PHP Coding Standards: 3.13.5
- WordPress Coding Standards: 3.3.0
- Plugin Check (PCP): 1.8.0
- Dashboard widget now correctly counts only vulnerabilities from enabled components, excluding disabled ones from settings.
- Status badge calculation (Critical/Warning) now properly considers only enabled components when determining severity level.
- Fixed PHPCS warnings for global variables without plugin prefix in wpvulnerability-admin.php and wpvulnerability-adminms.php.
- WordPress: 4.7 - 6.9
- PHP: 5.6 - 8.5
- WP-CLI: 2.3.0 - 2.11.0
- PHP Coding Standards: 3.13.5
- WordPress Coding Standards: 3.3.0
- Plugin Check (PCP): 1.8.0
- Complete Admin Interface Redesign: Modern card-based layout with visual component cards, improved spacing, color-coded status badges, and responsive grid layouts across all Settings tabs (Security, About, Logs, Tools, Analysis, and Notifications).
- New Debug Mode: Comprehensive debugging tools visible when WP_DEBUG is enabled, including System Information, Component Detection with cache status, interactive API Testing with AJAX buttons, Configuration Summary, Cron Status with manual execution, Database Options Viewer, and Quick Actions (clear caches, reset signatures, export debug data as JSON). Includes enhanced web server detection for 9 different servers.
- Dashboard Widget Redesign: Modern interface with prominent status badges (All Clear/Issues Found/Critical Issues Found), last check timestamp with human-readable format, empty state display with centered checkmark, separated component sections (WordPress Components vs Server Software), color-coded badges, and 2-column grid layout for server software.
- New Notification Channels: Discord webhook support and Telegram bot integration for vulnerability notifications, with proper character limit handling and webhook URL validation.
- Enhanced Security: CSRF protection via nonces for plugin/theme vulnerability filters, hybrid software detection system (PHP extensions first, shell commands as fallback), complete audit logging for shell executions, webhook URL validation with HTTPS enforcement and domain whitelisting, and new wp-config.php security constants.
- Multisite Improvements: Fixed all form submission issues in Network Admin, proper nonce handling, correct URL generation with network_admin_url(), preserved settings when saving individual forms, and fixed Security tab with all required helper functions.
- Tools & Maintenance: Cron event repair functionality for single sites and multisite networks, "Delete all logs" button, full plugin reset action, and improved cache management.
- Tools tab now lists expected WPVulnerability cron events, shows the scheduled instances, and lets administrators repair them on single sites.
- Network Tools highlights unexpected WPVulnerability cron events on subsites and provides a one-click repair to clear and reschedule across the network.
- Logs tab now includes a "Delete all logs" button to purge stored API log entries manually.
- Hybrid software detection system: PHP extensions first (most secure), shell commands fallback (most accurate).
- Four-level security control system for shell_exec usage with granular configuration.
- Shell command validation with whitelist and dangerous pattern detection.
- Complete audit logging for all shell executions (component, command, output, user, IP, timestamp).
- New wp-config.php constants:
WPVULNERABILITY_DISABLE_SHELL_EXEC,WPVULNERABILITY_SECURITY_MODE,WPVULNERABILITY_SHELL_EXEC_WHITELIST. - Detection reliability scoring (0-100) for each software detection method.
- Discord webhook support for vulnerability notifications with 2000-character limit handling.
- Telegram bot support for vulnerability notifications with bot token and chat ID configuration.
- Documentation links for Discord webhook setup (https://support.discord.com/hc/articles/228383668).
- Documentation links for Telegram bot setup (https://core.telegram.org/bots).
- Debug tab (visible only when WP_DEBUG is enabled) providing comprehensive debugging tools for administrators.
- wpvulnerability-debug.php file with 11 helper functions for debug functionality (~18KB).
- Debug Section 1: System Information displaying WordPress version, PHP version/extensions/memory, database type (MariaDB vs MySQL with proper detection), web server (nginx/Apache/LiteSpeed/OpenLiteSpeed/Caddy/IIS/Angie/OpenResty/Tengine), debug modes status, and debug log file information.
- Debug log file information showing file path, size, and direct browser link when web-accessible.
- Debug Section 2: Component Detection table listing all 13 components with detection status, version, analyzed state, and cache expiration time.
- Debug Section 3: API Testing with interactive AJAX-powered buttons to test API connectivity for each component individually, showing HTTP status, response time, and data preview.
- Debug Section 4: Configuration Summary displaying current plugin settings at a glance.
- Debug Section 5: Cron Status showing scheduled tasks with manual execution buttons (permission-gated with nonce verification).
- Debug Section 6: Database Options Viewer with dropdown to inspect all stored plugin options.
- Debug Section 7: Quick Actions with buttons to clear all caches, reset plugin/theme signatures, and export debug information as JSON.
- Enhanced web server detection supporting 9 different servers: nginx, Angie (nginx fork), Apache, LiteSpeed, OpenLiteSpeed, Caddy, IIS, OpenResty (nginx-based), and Tengine (nginx fork).
- Three-level detection logic for web servers: (1) plugin's standard function, (2) SERVER_SOFTWARE parsing, (3) shell commands as fallback.
- Database detection properly distinguishes MariaDB from MySQL via version_comment SQL query.
- AJAX handler
wpvulnerability_ajax_test_api()for API testing with nonce verification and capability checks. - Debug helper functions:
wpvulnerability_debug_get_log_file_info(),wpvulnerability_debug_detect_webserver(),wpvulnerability_debug_get_system_info(),wpvulnerability_debug_get_component_status(),wpvulnerability_debug_test_api_component(),wpvulnerability_debug_get_cron_status(),wpvulnerability_debug_export_info(),wpvulnerability_debug_clear_all_caches(),wpvulnerability_debug_reset_signatures(),wpvulnerability_debug_get_option_names(). - Debug tab POST handlers in both wpvulnerability-admin.php and wpvulnerability-adminms.php with nonce verification for all actions.
- Debug tab render functions in wpvulnerability-admin.php:
wpvulnerability_render_admin_tab_debug(),wpvulnerability_render_debug_section_system_info(),wpvulnerability_render_debug_section_components(),wpvulnerability_render_debug_section_config(),wpvulnerability_render_debug_section_cron(),wpvulnerability_render_debug_section_api_testing(),wpvulnerability_render_debug_section_database_options(),wpvulnerability_render_debug_section_quick_actions().
- Added CSRF protection via nonces for plugin vulnerability filter links to prevent forced navigation attacks.
- Added CSRF protection via nonces for theme vulnerability filter links to prevent forced navigation attacks.
- Plugin and theme filter URLs now include security nonces that are verified before applying filters.
- Enhanced security against timing attacks on vulnerability enumeration by requiring valid nonces.
- Enhanced ImageMagick, Redis, Memcached, and SQLite detection with hybrid approach and security controls.
- All shell commands hardcoded and validated - no user input involved.
- Shell execution wrapper with complete security checks and logging.
- Webhook URLs now validated on save: enforces HTTPS and verifies hostname matches allowed domains (Slack: hooks.slack.com, Teams: office.com/office365.com/api.hooks.microsoft.com, Discord: discord.com/discordapp.com).
- Telegram bot token validation with regex pattern check (format: 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11).
- Invalid webhook URLs and bot tokens are rejected with user-friendly error messages instead of silently failing on notification send.
- Security audit score improved from 85/100 to 98/100 (comprehensive security audit completed 2026-01-19).
- Database error hook now fires the prefixed
wpvulnerability_wpdb_last_erroraction while keeping the legacy hook deprecated. - Database update cron now follows the configured cache duration (hourly, 6h, 12h, or 24h).
- Translations load on init to avoid early textdomain warnings.
- Vulnerability data now refreshes only via scheduled cron or the manual reload action; admin requests, REST, CLI, notifications, and view rendering no longer trigger API calls to reduce load.
- Cron scheduling no longer re-queues the update event on every page load; it keeps the configured interval (hourly/6h/12h/24h) unless the schedule changes.
- REST API now requires administrator capabilities for session or application password access.
- Admin reset and test email actions enforce admin capabilities.
- API client timeouts corrected to 2.5 seconds to avoid long hangs.
- Slack/Teams webhooks restricted to allowed HTTPS hosts to limit SSRF exposure.
- Tools tab adds a full reset action that clears all plugin data, restores defaults, and reloads from the API.
- Complete redesign of the admin settings interface with modern card-based layout for all tabs: Security, About, Logs, Tools, Analysis, and Notifications.
- Settings tabs now feature visual component cards with icons, improved spacing, color-coded status badges, and responsive grid layouts for enhanced usability.
- Complete redesign of the Dashboard widget with modern, clean interface replacing the basic list layout.
- Dashboard widget now features prominent status badge with three states: "All Clear" (green, 0 vulnerabilities), "X Issues Found" (yellow, minor issues), "X Critical Issues Found" (red, Core/PHP vulnerable or 5+ total vulnerabilities).
- Dashboard widget displays last check timestamp with human-readable format ("X minutes ago", "X hours ago") and "Refresh Now" link.
- Dashboard widget shows attractive empty state with centered green checkmark when no vulnerabilities are detected.
- Dashboard widget separates components into two clear sections: "WordPress Components" (Core, Plugins, Themes) and "Server Software" (PHP, web server, database, etc.).
- Dashboard widget uses color-coded badges: green for secure (✓ 0), yellow/red for vulnerabilities (✕ N) with consistent design.
- Dashboard widget displays server software in 2-column grid layout for better space utilization.
- Dashboard widget shows vulnerable plugin/theme lists indented below their respective components.
- Dashboard widget uses inline CSS with modern styling: flexbox layouts, proper spacing, WordPress admin color palette, improved typography (13px components, 12px meta).
- Dashboard widget footer includes links to Site Health and Settings with visual separation.
- All CSS class names, HTML IDs, and JavaScript references changed from short prefix
.wpv-to full prefix.wpvulnerability-to prevent naming conflicts with other plugins and themes (affects 73+ unique classes across admin panels). - All inline CSS from admin panels moved to external assets/admin.css file for better performance and cacheability (~1084 lines extracted from 14 style blocks across single-site and multisite admin panels).
- License updated from GPL2+ to GPL3+.
- Saving partial forms (e.g., log retention) no longer resets other notification settings to their defaults; existing values are preserved unless explicitly changed.
- Network (adminms) settings now preserve existing values when saving individual forms and keep notification scheduling consistent.
- Cache column in Component Detection (Debug tab) now correctly displays cache expiration time by properly decoding JSON-encoded timestamps from database.
- Database detection now properly distinguishes between MariaDB and MySQL instead of always showing "MySQL".
- Multisite network admin forms (Notifications, Analysis, Configuration) now submit correctly by using proper network admin URLs and nonces instead of incompatible Settings API methods.
- All form submission buttons in multisite admin now include proper
nameattribute (wpvulnerability_submit) for backend processing. - Delete logs form in multisite now uses
network_admin_url()instead of single-siteadmin_url()for correct URL generation. - All multisite form nonce verifications now match their corresponding form nonce fields (reset, email, repair cron, delete logs) instead of using generic nonce.
- Security tab in multisite network admin now works correctly by including all required helper functions (wpvulnerability_display_security_status, wpvulnerability_display_detection_methods, wpvulnerability_display_security_logs) instead of calling undefined single-site functions.
- Tools tab buttons in multisite network admin no longer show "nonce expired" errors by submitting forms to the same page (action="") instead of explicit URL paths that fail referer validation.
- Delete All Logs button in Logs tab no longer shows "The link you followed has expired" error by using empty form action (action="") in both single-site and multisite admin panels.
- Logs tab pagination now displays horizontally instead of vertically by properly targeting list elements (ul with inline-flex) and individual page links (a and span within li) to work correctly with WordPress paginate_links() 'type' => 'list' output.
- WordPress: 4.7 - 6.9
- PHP: 5.6 - 8.5
- WP-CLI: 2.3.0 - 2.11.0
- PHP Coding Standards: 3.13.5
- WordPress Coding Standards: 3.3.0
- Plugin Check (PCP): 1.8.0
- Fixed authorization vulnerability in REST API endpoints that allowed low-privileged users to access sensitive vulnerability data. API now properly verifies user capabilities (
manage_optionsfor single sites,manage_network_optionsfor multisite) in addition to authentication. - Added direct access protection to wpvulnerability-api.php to prevent direct file execution outside WordPress context.
- WordPress: 4.7 - 6.9
- PHP: 5.6 - 8.4
- WP-CLI: 2.3.0 - 2.11.0
- PHP Coding Standards: 3.13.5
- WordPress Coding Standards: 3.3.0
- Plugin Check (PCP): 1.8.0
- Clear legacy WPVulnerability cron events from multisite subsites so updates and log cleanup only run on the main site.
- WordPress: 4.7 - 6.9
- PHP: 5.6 - 8.4
- WP-CLI: 2.3.0 - 2.11.0
- PHP Coding Standards: 3.13.5
- WordPress Coding Standards: 3.3.0
- Plugin Check (PCP): 1.7.0