[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fqcwm_GNukSh1rTC9V5bVXPPMXladRWu7TZSfc1KDGM4":3,"$fJSg3K_yUHMsiAmDmQ4HQwaHH02OKJJcZDt4e6jfhnj8":134,"$fFwkjv3mR63rFbLju4txqEvuxBtDlIxIh7ogGTNC2G-E":139},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"discovery_status":28,"vulnerabilities":29,"developer":30,"crawl_stats":26,"alternatives":35,"analysis":26,"fingerprints":26},"sitemedic-rescue-toolkit","SiteMedic Rescue Toolkit","2.4.6","prakashghai","https:\u002F\u002Fprofiles.wordpress.org\u002Fprakashghai\u002F","\u003Cp>SiteMedic Rescue Toolkit is a WordPress troubleshooting, diagnostics, and recovery helper plugin built for site owners, freelancers, agencies, and support teams who need a clear view of what may be wrong with a WordPress website.\u003C\u002Fp>\n\u003Cp>The plugin helps you check common WordPress problems from inside the dashboard, including site health issues, plugin risks, debug log entries, file permissions, security settings, performance problems, database status, rewrite rules, and system configuration concerns.\u003C\u002Fp>\n\u003Cp>SiteMedic is designed to help with situations such as:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>WordPress errors and warnings\u003C\u002Fli>\n\u003Cli>Plugin conflict diagnosis\u003C\u002Fli>\n\u003Cli>White screen or fatal error investigation\u003C\u002Fli>\n\u003Cli>Debug log review\u003C\u002Fli>\n\u003Cli>File permission checks\u003C\u002Fli>\n\u003Cli>XML-RPC and user enumeration checks\u003C\u002Fli>\n\u003Cli>Security header checks\u003C\u002Fli>\n\u003Cli>Admin account review\u003C\u002Fli>\n\u003Cli>Database and performance review\u003C\u002Fli>\n\u003Cli>Basic cleanup and repair guidance\u003C\u002Fli>\n\u003Cli>Support request preparation\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>All built-in local tools included in this WordPress.org version are available without a license key, payment, trial, quota, or time restriction.\u003C\u002Fp>\n\u003Cp>Optional professional help and optional paid upgrade options may be shown separately. They are not required to use the free tools included in this WordPress.org version.\u003C\u002Fp>\n\u003Ch3>Key Features\u003C\u002Fh3>\n\u003Ch4>Website Health Dashboard\u003C\u002Fh4>\n\u003Cp>Get a quick overview of your website condition, including WordPress version, PHP version, memory limit, active plugins, theme, database connection, and detected issues.\u003C\u002Fp>\n\u003Ch4>WordPress Diagnostics\u003C\u002Fh4>\n\u003Cp>Run local checks for common WordPress problems and review important technical details without manually searching through hosting panels or server files.\u003C\u002Fp>\n\u003Ch4>Debug Log Review\u003C\u002Fh4>\n\u003Cp>Check whether your website has generated a debug log and quickly move to the Debug Analyzer for further investigation.\u003C\u002Fp>\n\u003Ch4>Plugin and Risk Scanners\u003C\u002Fh4>\n\u003Cp>Review active plugins, possible risk indicators, and common troubleshooting signals that may help identify broken-site or conflict situations.\u003C\u002Fp>\n\u003Ch4>Security Checks\u003C\u002Fh4>\n\u003Cp>Review file permissions, XML-RPC exposure, user enumeration risks, security headers, and admin account concerns.\u003C\u002Fp>\n\u003Ch4>Performance and Database Review\u003C\u002Fh4>\n\u003Cp>Check performance-related signals, database status, plugin load concerns, cache detection, images, and hosting-related basics.\u003C\u002Fp>\n\u003Ch4>Safe Repair Guidance\u003C\u002Fh4>\n\u003Cp>Use built-in guidance and repair options for common WordPress maintenance and troubleshooting tasks such as cleanup, rewrite rule repair, debug review, and system checks.\u003C\u002Fp>\n\u003Ch4>Expert Help Option\u003C\u002Fh4>\n\u003Cp>If your website shows issues you cannot resolve yourself, SiteMedic can guide you toward optional professional support from WP Official Support.\u003C\u002Fp>\n\u003Ch3>Why Use SiteMedic Rescue Toolkit?\u003C\u002Fh3>\n\u003Cp>SiteMedic Rescue Toolkit helps reduce guesswork when something goes wrong with a WordPress website.\u003C\u002Fp>\n\u003Cp>Instead of jumping between multiple plugins, hosting tools, logs, and settings screens, SiteMedic brings common diagnostic checks into one WordPress dashboard.\u003C\u002Fp>\n\u003Cp>Use it when you want to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Understand why a WordPress site may be unstable\u003C\u002Fli>\n\u003Cli>Check common technical issues before contacting support\u003C\u002Fli>\n\u003Cli>Review debug and security signals\u003C\u002Fli>\n\u003Cli>Prepare a clearer support request\u003C\u002Fli>\n\u003Cli>Detect plugin, performance, or configuration concerns\u003C\u002Fli>\n\u003Cli>Get a safer starting point before making repair decisions\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Free Version\u003C\u002Fh3>\n\u003Cp>The WordPress.org version includes local diagnostic, troubleshooting, reporting, and guidance tools.\u003C\u002Fp>\n\u003Cp>No license key is required to use the included free tools.\u003C\u002Fp>\n\u003Ch3>Optional Pro Upgrade\u003C\u002Fh3>\n\u003Cp>SiteMedic may show optional upgrade information for users who want advanced recovery tools or priority expert assistance.\u003C\u002Fp>\n\u003Cp>Optional paid plans are handled separately by WP Official Support and are not required to use the free tools in this plugin.\u003C\u002Fp>\n\u003Cp>The optional Pro version may include advanced emergency recovery tools such as:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Emergency Rescue URL\u003C\u002Fli>\n\u003Cli>White screen recovery support\u003C\u002Fli>\n\u003Cli>Fatal error investigation tools\u003C\u002Fli>\n\u003Cli>Plugin conflict recovery tools\u003C\u002Fli>\n\u003Cli>Theme fallback recovery guidance\u003C\u002Fli>\n\u003Cli>.htaccess repair tools\u003C\u002Fli>\n\u003Cli>wp-config safety checks\u003C\u002Fli>\n\u003Cli>Database connection diagnostics\u003C\u002Fli>\n\u003Cli>Support Access tool\u003C\u002Fli>\n\u003Cli>Priority expert help options\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>External Services\u003C\u002Fh3>\n\u003Cp>This plugin may connect to external services only when a site administrator chooses to open optional upgrade or support areas.\u003C\u002Fp>\n\u003Cp>The free local diagnostic tools do not require payment or a license key.\u003C\u002Fp>\n\u003Ch4>WP Official Support\u003C\u002Fh4>\n\u003Cp>Service: WP Official Support\u003Cbr \u002F>\nPurpose: Optional professional website troubleshooting services, optional upgrade information, pricing configuration, and paid plan delivery.\u003Cbr \u002F>\nData sent automatically: When an administrator opens the optional upgrade screen, the plugin may request public plan information from WP Official Support. This request may include normal browser\u002Fserver request data such as IP address, user agent, and referrer. No website diagnostic report is automatically sent by this request.\u003Cbr \u002F>\nWebsite: https:\u002F\u002Fwww.wpofficialsupport.com\u002F\u003Cbr \u002F>\nPrivacy Policy: https:\u002F\u002Fwww.wpofficialsupport.com\u002Fprivacy-policy\u002F\u003Cbr \u002F>\nTerms: https:\u002F\u002Fwww.wpofficialsupport.com\u002Fterms-and-conditions\u002F\u003C\u002Fp>\n\u003Ch4>PayPal\u003C\u002Fh4>\n\u003Cp>Service: PayPal\u003Cbr \u002F>\nPurpose: Optional paid subscription checkout for SiteMedic Pro or Pro Plus plans.\u003Cbr \u002F>\nData sent automatically: PayPal checkout scripts may load only on the optional upgrade screen. PayPal may receive standard browser request data and payment-related information when the administrator chooses to use PayPal checkout.\u003Cbr \u002F>\nWebsite: https:\u002F\u002Fwww.paypal.com\u002F\u003Cbr \u002F>\nPrivacy Policy: https:\u002F\u002Fwww.paypal.com\u002Fprivacy\u002F\u003Cbr \u002F>\nTerms: https:\u002F\u002Fwww.paypal.com\u002Flegalhub\u002Fuseragreement-full\u002F\u003C\u002Fp>\n","Diagnose and safely repair WordPress issues with site health, debug, security, cleanup, and recovery tools.",0,129,"2026-06-22T06:54:00.000Z","7.0.2","5.8","7.4",[18,19,20,21,22],"debug","recovery","security","site-health","troubleshooting","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsitemedic-rescue-toolkit.zip",100,null,"2026-07-22T17:31:50.256Z","no_bundle",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":25,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},1,30,94,"2026-08-29T11:21:45.436Z",[36,56,76,94,113],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":46,"num_ratings":47,"last_updated":48,"tested_up_to":14,"requires_at_least":49,"requires_php":50,"tags":51,"homepage":54,"download_link":55,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"wp-safe-mode","WP Safe Mode","1.3","Marcus (aka @msykes)","https:\u002F\u002Fprofiles.wordpress.org\u002Fnetweblogic\u002F","\u003Cp>WP Safe Mode allows you to view your site temporarily with certain plugins disabled\u002Fenabled as well as switching to another theme.\u003C\u002Fp>\n\u003Cp>This is particularly useful if you are experiencing problems with a specific plugin or theme and need troubleshoot without it affecting the rest of your site visitors.\u003C\u002Fp>\n\u003Cp>Additionally, a loader file can be directly installed via FTP to help you access an inaccessible site due to PHP errors (e.g. blank screens or white screen of death) to help restore it from the admin panel.\u003C\u002Fp>\n\u003Ch4>Main Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Enter Safe Mode for just yourself whilst logged in.\u003C\u002Fli>\n\u003Cli>Enable Safe Mode for the whole site.\u003C\u002Fli>\n\u003Cli>Admin Bar shortcuts for enabling\u002Fdisabling Safe Mode.\u003C\u002Fli>\n\u003Cli>Restrict Safe Mode to certain IP addresses.\u003C\u002Fli>\n\u003Cli>Automatic installation (if file permissions allow).\u003C\u002Fli>\n\u003Cli>Fallback to a default WordPress theme or one of your choice in Safe Mode.\u003C\u002Fli>\n\u003Cli>Prevent or allow Must-Use plugins from loading in Safe-Mode.\u003C\u002Fli>\n\u003Cli>Handy loader file via FTP when your site is completely inaccessible.\u003C\u002Fli>\n\u003Cli>MultiSite Support\n\u003Cul>\n\u003Cli>Network-wide Safe Mode (for just you, or everyone)\u003C\u002Fli>\n\u003Cli>Restrict Network-wide Safe Mode to certain IP address\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>MultiSite Site-Specific Safe Modes\n\u003Cul>\n\u003Cli>Override Network-wide Safe Mode settings for an individual site\u003C\u002Fli>\n\u003Cli>Network Admins can deactivate Network-Active and Must-Use plugins.\u003C\u002Fli>\n\u003Cli>Allow individual site admins from enabling safe mode for their own site.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Data Privacy and GDPR Compliance\u003C\u002Fh4>\n\u003Cp>No personal data is used or stored by this plugin. For those entering user-only mode, a cookie is loaded to identify that user.\u003C\u002Fp>\n","Disable plugins or switch themes for just you or the whole site for debugging, troubleshooting or accessing and restoring a broken website.",2000,25146,86,8,"2026-05-23T16:03:00.000Z","4.6","5.2.6",[18,52,19,53,22],"debugging","safe-mode","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-safe-mode\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-safe-mode.1.3.zip",{"slug":57,"name":58,"version":59,"author":60,"author_profile":61,"description":62,"short_description":63,"active_installs":25,"downloaded":64,"rating":25,"num_ratings":65,"last_updated":66,"tested_up_to":67,"requires_at_least":68,"requires_php":69,"tags":70,"homepage":73,"download_link":74,"security_score":75,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"site-health-manager","Site Health Manager","1.1.2","Rami Yushuvaev","https:\u002F\u002Fprofiles.wordpress.org\u002Framiy\u002F","\u003Cp>Make sure your health score is correct by running only the tests relevant to your server configuration. Take some protective measures to keep your critical server data hidden and secure.\u003C\u002Fp>\n\u003Ch4>Status Manager\u003C\u002Fh4>\n\u003Cp>Site Health Status screen generates a health score based on tests it runs on the server, but some tests may not be relevant to your server setup. This may cause a low health score, unhappy site owners, and complaints for web hosts.\u003C\u002Fp>\n\u003Cp>Select the test you want to disable in order to prevent displaying the wrong health score in your Site Health Status screen. For example, missing PHP extensions for security reasons or disabled background updates to allow version control.\u003C\u002Fp>\n\u003Ch4>Info Manager\u003C\u002Fh4>\n\u003Cp>Site Health Info screen displays configuration data and debugging information. Some data in this screen is confidential and sharing critical server data should be done with caution and with security in mind.\u003C\u002Fp>\n\u003Cp>Select what information you want to disable in order to prevent your users from copying it to the clipboard when sharing debug data with third parties. For example, when sending data to plugin\u002Ftheme developers to debug issues.\u003C\u002Fp>\n\u003Ch4>Contribute\u003C\u002Fh4>\n\u003Cp>If you want to contribute, visit \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Framiy\u002Fsite-health-manager\" rel=\"nofollow ugc\">Site Health Manager GitHub Repository\u003C\u002Fa> and see where you can help.\u003C\u002Fp>\n\u003Cp>You can also help by translating the plugin to your language via \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fsite-health-manager\u002F\" rel=\"nofollow ugc\">translate.wordpress.org\u003C\u002Fa>.\u003C\u002Fp>\n","Control which status tests and what debug information appear in your Site Health screen.",4155,4,"2019-06-20T12:58:00.000Z","5.2.24","5.2","5.6",[71,18,72,20,21],"confidential-data","health","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsite-health-manager\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsite-health-manager.1.1.2.zip",85,{"slug":77,"name":78,"version":79,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":11,"downloaded":84,"rating":11,"num_ratings":11,"last_updated":85,"tested_up_to":86,"requires_at_least":87,"requires_php":88,"tags":89,"homepage":23,"download_link":92,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":93},"mrqurban-emergency-rescue","MrQurban Emergency Rescue","1.1.0","Muhammad Qurban","https:\u002F\u002Fprofiles.wordpress.org\u002Fmrqurban13\u002F","\u003Cp>\u003Cstrong>MrQurban Emergency Rescue\u003C\u002Fstrong> is a lightweight, life-saving plugin designed to help you recover your WordPress site when you are locked out of the admin panel due to a fatal error, “Critical Error,” or the dreaded White Screen of Death (WSOD).\u003C\u002Fp>\n\u003Cp>It provides a \u003Cstrong>Secret Rescue URL\u003C\u002Fstrong> that loads a minimal, fail-safe interface \u003Cem>before\u003C\u002Fem> your active plugins, allowing you to selectively disable problematic plugins or themes by renaming their folders without needing FTP access.\u003C\u002Fp>\n\u003Ch3>🌟 Key Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Fail-Safe Recovery\u003C\u002Fstrong>: Loads early to bypass fatal errors caused by other plugins.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Secret Access\u003C\u002Fstrong>: Protected by a unique, randomized secret key.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>One-Click Deactivation\u003C\u002Fstrong>: Instantly disable any plugin or theme.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debug Tools\u003C\u002Fstrong>: Enable \u003Ccode>WP_DEBUG_LOG\u003C\u002Fcode> on the fly and view the log file directly in the rescue interface.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Secure\u003C\u002Fstrong>: Uses a secret key and verifies permissions.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>⚠️ Important Usage Note\u003C\u002Fh3>\n\u003Cp>While this plugin works as a standard plugin, it is \u003Cstrong>highly recommended\u003C\u002Fstrong> to install it as a \u003Cstrong>Must-Use (MU) Plugin\u003C\u002Fstrong> to ensure it loads before any other plugin that might be causing a crash.\u003C\u002Fp>\n","Recover from fatal errors and White Screen of Death (WSOD) by disabling plugins or themes via a secret rescue URL.",283,"2026-03-16T18:39:00.000Z","6.9.4","5.0","7.0",[18,90,19,91,22],"fatal-error","rescue","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmrqurban-emergency-rescue.1.1.zip","2026-04-16T10:56:18.058Z",{"slug":95,"name":96,"version":97,"author":98,"author_profile":99,"description":100,"short_description":101,"active_installs":102,"downloaded":103,"rating":25,"num_ratings":104,"last_updated":105,"tested_up_to":106,"requires_at_least":69,"requires_php":88,"tags":107,"homepage":109,"download_link":110,"security_score":111,"vuln_count":31,"unpatched_count":11,"last_vuln_date":112,"fetched_at":27},"wpvulnerability","WPVulnerability","5.1.1","Javier Casares","https:\u002F\u002Fprofiles.wordpress.org\u002Fjaviercasares\u002F","\u003Cp>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.\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch4>Data reliability\u003C\u002Fh4>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch3>Using the plugin\u003C\u002Fh3>\n\u003Ch4>WP-CLI\u003C\u002Fh4>\n\u003Cp>You can use the following WP-CLI commands to manage and check vulnerabilities:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Core: \u003Ccode>wp wpvulnerability core\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Plugins: \u003Ccode>wp wpvulnerability plugins\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Themes: \u003Ccode>wp wpvulnerability themes\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>PHP: \u003Ccode>wp wpvulnerability php\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Apache HTTPD: \u003Ccode>wp wpvulnerability apache\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>nginx: \u003Ccode>wp wpvulnerability nginx\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>MariaDB: \u003Ccode>wp wpvulnerability mariadb\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>MySQL: \u003Ccode>wp wpvulnerability mysql\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>ImageMagick: \u003Ccode>wp wpvulnerability imagemagick\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>curl: \u003Ccode>wp wpvulnerability curl\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>memcached: \u003Ccode>wp wpvulnerability memcached\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Redis: \u003Ccode>wp wpvulnerability redis\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>SQLite: \u003Ccode>wp wpvulnerability sqlite\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>To configure the plugin you can use:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Hide component: \u003Ccode>wp wpvulnerability config hide \u003Ccomponent> [on|off]\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Notification email: \u003Ccode>wp wpvulnerability config email \u003Cemails>\u003C\u002Fcode> (comma separatted)\u003C\u002Fli>\n\u003Cli>Notification period: \u003Ccode>wp wpvulnerability config period \u003Cnever|daily|weekly>\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Log retention: \u003Ccode>wp wpvulnerability config log-retention \u003C0|1|7|14|28>\u003C\u002Fcode> (in days)\u003C\u002Fli>\n\u003Cli>Cache duration: \u003Ccode>wp wpvulnerability config cache \u003C1|6|12|24>\u003C\u002Fcode> (in hours)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>All commands support the \u003Ccode>--format\u003C\u002Fcode> option to specify the output format:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>--format=table\u003C\u002Fcode>: Displays the results in a table format (default).\u003C\u002Fli>\n\u003Cli>\u003Ccode>--format=json\u003C\u002Fcode>: Displays the results in JSON format.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Need help?\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp wpvulnerability --help\u003C\u002Fcode>: Displays help information for WPVulnerability commands.\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp wpvulnerability [command] --help\u003C\u002Fcode>: Displays help information for a WPVulnerability command.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>REST API\u003C\u002Fh4>\n\u003Cp>The WPVulnerability plugin provides several \u003Cstrong>REST API endpoints\u003C\u002Fstrong> to fetch vulnerability information for different components of your WordPress site.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Core: \u003Ccode>\u002Fwpvulnerability\u002Fv1\u002Fcore\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Plugins: \u003Ccode>\u002Fwpvulnerability\u002Fv1\u002Fplugins\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Themes: \u003Ccode>\u002Fwpvulnerability\u002Fv1\u002Fthemes\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>PHP: \u003Ccode>\u002Fwpvulnerability\u002Fv1\u002Fphp\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Apache HTTPD: \u003Ccode>\u002Fwpvulnerability\u002Fv1\u002Fapache\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>nginx: \u003Ccode>\u002Fwpvulnerability\u002Fv1\u002Fnginx\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>MariaDB: \u003Ccode>\u002Fwpvulnerability\u002Fv1\u002Fmariadb\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>MySQL: \u003Ccode>\u002Fwpvulnerability\u002Fv1\u002Fmysql\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>ImageMagick: \u003Ccode>\u002Fwpvulnerability\u002Fv1\u002Fimagemagick\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>curl: \u003Ccode>\u002Fwpvulnerability\u002Fv1\u002Fcurl\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>memcached: \u003Ccode>\u002Fwpvulnerability\u002Fv1\u002Fmemcached\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Redis: \u003Ccode>\u002Fwpvulnerability\u002Fv1\u002Fredis\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>SQLite: \u003Ccode>\u002Fwpvulnerability\u002Fv1\u002Fsqlite\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The WPVulnerability REST API uses \u003Cstrong>Application Passwords\u003C\u002Fstrong> for authentication. You need to include a valid Application Password in the Authorization header of your requests.\u003C\u002Fp>\n\u003Cp>Example Request with Authentication\u003C\u002Fp>\n\u003Cpre>\u003Ccode>curl -X GET https:\u002F\u002Fexample.com\u002Fwp-json\u002Fwpvulnerability\u002Fv1\u002Fplugins -u username:application_password\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Replace username with your WordPress \u003Ccode>username\u003C\u002Fcode> and \u003Ccode>application_password\u003C\u002Fcode> with your \u003Ca href=\"https:\u002F\u002Fmake.wordpress.org\u002Fcore\u002F2020\u002F11\u002F05\u002Fapplication-passwords-integration-guide\u002F\" rel=\"nofollow ugc\">Application Password\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Extra Configurations\u003C\u002Fh3>\n\u003Ch4>“From:” mail (since: 3.2.2)\u003C\u002Fh4>\n\u003Cp>If, for some reason, you need the emails sent by the plugin to have a From different from the site administrator, you can change it from the \u003Ccode>wp-config.php\u003C\u002Fcode> by adding a constant:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WPVULNERABILITY_MAIL', 'sender@example.com' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If the constant is active, it will be visible in the configuration screen.\u003C\u002Fp>\n\u003Ch4>Force hiding checks (since: 4.1.0)\u003C\u002Fh4>\n\u003Cp>If you want to always hide a specific component, you can define a constant in \u003Ccode>wp-config.php\u003C\u002Fcode>. When set to \u003Ccode>true\u003C\u002Fcode>, the option will be checked automatically in the settings screen and the related analysis will be skipped.\u003C\u002Fp>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WPVULNERABILITY_HIDE_APACHE', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Available constants: \u003Ccode>WPVULNERABILITY_HIDE_CORE\u003C\u002Fcode>, \u003Ccode>WPVULNERABILITY_HIDE_PLUGINS\u003C\u002Fcode>, \u003Ccode>WPVULNERABILITY_HIDE_THEMES\u003C\u002Fcode>, \u003Ccode>WPVULNERABILITY_HIDE_PHP\u003C\u002Fcode>, \u003Ccode>WPVULNERABILITY_HIDE_APACHE\u003C\u002Fcode>, \u003Ccode>WPVULNERABILITY_HIDE_NGINX\u003C\u002Fcode>, \u003Ccode>WPVULNERABILITY_HIDE_MARIADB\u003C\u002Fcode>, \u003Ccode>WPVULNERABILITY_HIDE_MYSQL\u003C\u002Fcode>, \u003Ccode>WPVULNERABILITY_HIDE_IMAGEMAGICK\u003C\u002Fcode>, \u003Ccode>WPVULNERABILITY_HIDE_CURL\u003C\u002Fcode>, \u003Ccode>WPVULNERABILITY_HIDE_MEMCACHED\u003C\u002Fcode>, \u003Ccode>WPVULNERABILITY_HIDE_REDIS\u003C\u002Fcode>, \u003Ccode>WPVULNERABILITY_HIDE_SQLITE\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch4>Cache duration (since: 4.1.0)\u003C\u002Fh4>\n\u003Cp>By default, data from the API is cached for 12 hours. To change this, define \u003Ccode>WPVULNERABILITY_CACHE_HOURS\u003C\u002Fcode> in \u003Ccode>wp-config.php\u003C\u002Fcode> with one of \u003Ccode>1\u003C\u002Fcode>, \u003Ccode>6\u003C\u002Fcode>, \u003Ccode>12\u003C\u002Fcode> or \u003Ccode>24\u003C\u002Fcode>. This value overrides the setting screen and WP-CLI command.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WPVULNERABILITY_CACHE_HOURS', 24 );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Log rotation (since: 4.2.0)\u003C\u002Fh4>\n\u003Cp>WPVulnerability stores the most recent API responses so you can review recent calls from the new log tab. Define \u003Ccode>WPVULNERABILITY_LOG_RETENTION_DAYS\u003C\u002Fcode> in \u003Ccode>wp-config.php\u003C\u002Fcode> to control how many days of entries are preserved. Supported values are \u003Ccode>0\u003C\u002Fcode>, \u003Ccode>1\u003C\u002Fcode>, \u003Ccode>7\u003C\u002Fcode>, \u003Ccode>14\u003C\u002Fcode> or \u003Ccode>28\u003C\u002Fcode>; using \u003Ccode>0\u003C\u002Fcode> disables logging entirely.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WPVULNERABILITY_LOG_RETENTION_DAYS', 14 );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>When the constant is present its value is enforced in the settings UI and through WP-CLI, ensuring consistent log rotation across environments.\u003C\u002Fp>\n\u003Ch4>Security configuration (since: 4.3.0)\u003C\u002Fh4>\n\u003Cp>WPVulnerability uses a hybrid detection approach for server software (ImageMagick, Redis, Memcached, SQLite): PHP extensions first (most secure), then shell commands as fallback (most accurate). You can control this behavior using security configuration constants in \u003Ccode>wp-config.php\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Global disable of shell commands:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WPVULNERABILITY_DISABLE_SHELL_EXEC', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Completely disables shell command usage. Falls back to PHP extensions only. Use for maximum security when accuracy loss is acceptable.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Security mode (standard\u002Fstrict\u002Fdisabled):\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WPVULNERABILITY_SECURITY_MODE', 'strict' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cul>\n\u003Cli>\u003Ccode>standard\u003C\u002Fcode> – Hybrid detection: PHP extensions first, shell commands fallback (default, best accuracy)\u003C\u002Fli>\n\u003Cli>\u003Ccode>strict\u003C\u002Fcode> – PHP extensions only, no shell commands (high security, lower accuracy)\u003C\u002Fli>\n\u003Cli>\u003Ccode>disabled\u003C\u002Fcode> – No software detection at all (maximum security)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Component whitelist:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WPVULNERABILITY_SHELL_EXEC_WHITELIST', 'imagemagick,redis' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Allows shell commands only for specified components. Available components: \u003Ccode>imagemagick\u003C\u002Fcode>, \u003Ccode>redis\u003C\u002Fcode>, \u003Ccode>memcached\u003C\u002Fcode>, \u003Ccode>sqlite\u003C\u002Fcode>. Use for granular control.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Examples:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Maximum security (no shell commands):\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WPVULNERABILITY_SECURITY_MODE', 'strict' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Only allow ImageMagick shell detection:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WPVULNERABILITY_SHELL_EXEC_WHITELIST', 'imagemagick' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Complete disable:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WPVULNERABILITY_DISABLE_SHELL_EXEC', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>All shell commands are hardcoded and validated – no user input is involved. Commands are logged for security auditing.\u003C\u002Fp>\n\u003Ch3>Compatibility\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>WordPress: 5.6 – 7.1\u003C\u002Fli>\n\u003Cli>PHP: 7.0 – 8.5\u003C\u002Fli>\n\u003Cli>WP-CLI: 2.3.0 – 2.12.0\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Security\u003C\u002Fh3>\n\u003Cp>This plugin adheres to the following security measures and review protocols for each version:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Fplugins\u002F\" rel=\"nofollow ugc\">WordPress Plugin Handbook\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Fplugins\u002Fwordpress-org\u002Fplugin-security\u002F\" rel=\"nofollow ugc\">WordPress Plugin Security\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Fapis\u002Fsecurity\u002F\" rel=\"nofollow ugc\">WordPress APIs Security\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FWordPress\u002FWordPress-Coding-Standards\" rel=\"nofollow ugc\">WordPress Coding Standards\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fplugin-check\u002F\" rel=\"ugc\">Plugin Check (PCP)\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>This plugin or the WordPress Vulnerability Database API does not collect any information about your site, your identity, the plugins, themes or content the site has.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Vulnerabilities\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>A security vulnerability was found and fixed in version 4.2.2.1. All previous versions (3.3.0 – 4.2.1) are affected. Please update to version 4.2.2.1 or later.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Found a security vulnerability? Please report it to us privately at the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjaviercasares\u002Fwpvulnerability\u002Fsecurity\u002Fadvisories\u002Fnew\" rel=\"nofollow ugc\">WPVulnerability GitHub repository\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Contributors\u003C\u002Fh3>\n\u003Cp>You can contribute to this plugin at the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjaviercasares\u002Fwpvulnerability\" rel=\"nofollow ugc\">WPVulnerability GitHub repository\u003C\u002Fa>.\u003C\u002Fp>\n","Get WordPress vulnerability alerts from the WPVulnerability Database API.",10000,644570,20,"2026-07-09T06:33:00.000Z","7.1",[20,21,108],"vulnerability","https:\u002F\u002Fwww.wpvulnerability.com\u002Fplugin\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwpvulnerability.5.1.1.zip",99,"2026-03-18 00:00:00",{"slug":114,"name":115,"version":116,"author":117,"author_profile":118,"description":119,"short_description":120,"active_installs":121,"downloaded":122,"rating":123,"num_ratings":124,"last_updated":125,"tested_up_to":14,"requires_at_least":126,"requires_php":127,"tags":128,"homepage":132,"download_link":133,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"plugin-detective","Plugin Detective – Troubleshooting Conflicts","1.2.32","NSquared","https:\u002F\u002Fprofiles.wordpress.org\u002Fcroixhaug\u002F","\u003Cp>\u003Cstrong>Plugin Detective helps you troubleshoot issues on your site quickly and easily to find the cause of a problem.\u003C\u002Fstrong> Once the culprit is found, the problem plugin can be quickly deactivated. You can even fix your site when it has the white screen of death (fatal error). You’ll want to have Plugin Detective installed, so if your site crashes from a conflict or bad plugin update, you can get it back up and running quickly!\u003C\u002Fp>\n\u003Cp>Plugin Detective is your best friend when you need to:\u003Cbr \u002F>\n– Troubleshoot WordPress plugin conflicts\u003Cbr \u002F>\n– Remove stuck .maintenance files\u003Cbr \u002F>\n– Recover your site from fatal errors caused by plugins\u003C\u002Fp>\n\u003Cp>We’ve all been there–something’s broken on your site. You’ve looked around the web for advice about what to do and have stumbled across the typical wisdom: deactivate all your plugins and then reactivate them one by one, checking your site for the problem after each reactivation.\u003C\u002Fp>\n\u003Cp>Ugh.\u003C\u002Fp>\n\u003Cp>Sure, it works. But who has \u003Cem>time\u003C\u002Fem> for that?\u003C\u002Fp>\n\u003Cdiv class=\"embed-vimeo\" style=\"text-align: center;\">\u003Ciframe loading=\"lazy\" src=\"https:\u002F\u002Fplayer.vimeo.com\u002Fvideo\u002F270010645\" width=\"750\" height=\"422\" frameborder=\"0\" webkitallowfullscreen mozallowfullscreen allowfullscreen>\u003C\u002Fiframe>\u003C\u002Fdiv>\n\u003Ch4>Find Plugin Conflicts with Detective Otto Bot\u003C\u002Fh4>\n\u003Cp>Detective Otto Bot walks you through solving your case one step at a time, all from one single screen.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Open a case and tell Detective Otto where you’re seeing the problem. If your site requires any plugins to run correctly, tell Otto about those, too.\u003C\u002Fli>\n\u003Cli>Then, Otto will interrogate the suspects and track clues, checking in with you from time to time.\u003C\u002Fli>\n\u003Cli>All you need to do is answer “Yes, it’s fixed” or “No, it’s still broken” each time. Otto will do the rest and find the culprit in minutes.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Best of all – Plugin Detective can work even if you’re seeing the White Screen of Death on your site or if all you can see are PHP errors. Please have a look at the FAQ’s for how to access Plugin Detective and log into WordPress even if you can’t get to your login screen.\u003C\u002Fp>\n\u003Cp>Once Otto has identified the culprit, you can quickly deactivate the troublesome plugin and go about your day.\u003C\u002Fp>\n\u003Ch4>Remove Stuck .Maintenance File or Scheduled Maintenance\u003C\u002Fh4>\n\u003Cp>Have you gotten stuck in maintenance mode on WordPress? The dreaded “Briefly unavailable for scheduled maintenance. Check back in a minute” message haunts you; the minute never ends!\u003C\u002Fp>\n\u003Cp>With Plugin Detective installed you can quickly get out of these situations without the hassle of deleting files via your host or FTP. Just tack on this slug to the end of your website URL:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002Fwp-content\u002Fplugins\u002Fplugin-detective\u002Ftroubleshoot\u002F?restore=1\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>So that your URL looks like this:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>https:\u002F\u002Fyoursite.com\u002Fwp-content\u002Fplugins\u002Fplugin-detective\u002Ftroubleshoot\u002F?restore=1\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This will prompt you to log in and automatically remove that stuck maintenance file for you.\u003C\u002Fp>\n\u003Ch4>Who Can Use This Troubleshooting Tool?\u003C\u002Fh4>\n\u003Cp>Plugin Detective is a tool that requires no coding experience or technical knowledge to use. For that reason, Plugin Detective is the ideal troubleshooting and conflict-checking tool for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Any WordPress website owner\u003C\u002Fli>\n\u003Cli>Developers and technical support engineers\u003C\u002Fli>\n\u003Cli>Plugin and theme owners and their support teams\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Debug Tool Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Strategically activate and deactivate plugins on your site to help you find the plugin causing trouble\u003C\u002Fli>\n\u003Cli>Open Plugin Detective for troubleshooting on any page on your site – both in the backend and the frontend!\u003C\u002Fli>\n\u003Cli>Choose any subset of your active plugins as the baseline for your testing  \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Loved by Plugin Support Teams\u003C\u002Fh4>\n\u003Cp>The \u003Ca href=\"https:\u002F\u002Fsimplyscheduleappointments.com\u002Fguides\u002Fplugin-detective-for-plugin-conflicts\u002F\" rel=\"nofollow ugc\">Simply Schedule Appointments\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwpdrawattention.com\u002Fguides\u002Fplugin-detective-for-finding-conflicts\u002F\" rel=\"nofollow ugc\">Draw Attention\u003C\u002Fa> support teams love to share this conflict-checking tool with their customers.\u003Cbr \u002F>\nPlugin Detective makes it easy for their clients to debug performance issues and figure out plugin conflicts in a jiffy!\u003C\u002Fp>\n\u003Ch3>1.2.14 – 2023-06-10\u003C\u002Fh3>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Fix PHP 8.2 compatibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.2.13 – 2023-05-25\u003C\u002Fh3>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Update required WP version to 6.1\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.2.12 – 2023-05-25\u003C\u002Fh3>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Update required WP version to 6.1\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.2.11 – 2023-04-27\u003C\u002Fh3>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Cp>PR:#25 – Compatibility with WordPress 6.2\u003C\u002Fp>\n\u003Ch3>1.2.10 – 2023-04-11\u003C\u002Fh3>\n\u003Ch4>Fixes\u003C\u002Fh4>\n\u003Cp>PR:#19 – Prevent fatal error on WP versions where WP_Textdomain_Registry doesn…\u003C\u002Fp>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Ch3>1.2.9 – 2023-03-28\u003C\u002Fh3>\n\u003Ch4>Fixes\u003C\u002Fh4>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Ch3>1.2.8 – 2023-03-28\u003C\u002Fh3>\n\u003Ch4>Fixes\u003C\u002Fh4>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Ch3>1.2.7 – 2023-03-28\u003C\u002Fh3>\n\u003Ch4>Fixes\u003C\u002Fh4>\n\u003Ch4>Features and Improvements\u003C\u002Fh4>\n\u003Ch3>1.2.6 – 2023-02-24\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>no changes\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.2.3\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fixed for WP 6.1 compatibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.2.1\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fixed for WP 5.9 compatibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.1.8\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fixed for WP 5.8 compatibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>1.1.8\u003C\u002Fh3>\n\u003Cp>For older changelog entries, please see the \u003Ca href=\"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fplugin-detective\u002Ftrunk\u002FCHANGELOG.md\" rel=\"nofollow ugc\">additional changelog.txt file\u003C\u002Fa> delivered with the plugin.\u003C\u002Fp>\n","Quickly find and fix WordPress plugin conflicts, recover from fatal errors, and clear stuck maintenance mode without any coding.",5000,226251,80,48,"2026-07-01T16:47:00.000Z","6.1","5.3",[129,18,130,21,131],"conflicts","performance","troubleshoot","https:\u002F\u002Fnsquared.io","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fplugin-detective.1.2.32.zip",{"error":135,"url":136,"statusCode":137,"statusMessage":138,"message":138},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fsitemedic-rescue-toolkit\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":31,"versions":140},[141],{"version":142,"download_url":143,"svn_tag_url":144,"released_at":26,"has_diff":145,"diff_files_changed":146,"diff_lines":26,"trac_diff_url":26,"vulnerabilities":147,"is_current":145},"2.4.5","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsitemedic-rescue-toolkit.2.4.5.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fsitemedic-rescue-toolkit\u002Ftags\u002F2.4.5\u002F",false,[],[]]