[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$ffkhXnFuSyPNZe04lr_RFeFqx_H5CU9gV-cGCXeI-gDs":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":21,"download_link":22,"security_score":23,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25,"vulnerabilities":26,"developer":27,"crawl_stats":24,"alternatives":34,"analysis":141,"fingerprints":322},"wp-geeky-troubleshooter","WP Geeky Troubleshooter – Troubleshoot Your WordPress Site without FTP","1.0.0","Sandesh","https:\u002F\u002Fprofiles.wordpress.org\u002Fsandesh055\u002F","\u003Cp>\u003Cstrong>Troubleshoot WordPress Site Like Never Before\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Are you encountering WordPress errors on your site? Do you want to troubleshoot these WordPress errors on your own? Most of these errors can be solved by this plugin. It will help you to get back your site online without FTP.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Prevention is better than Cure\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Remote Access – Login without password\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Troubleshoot Theme and Plugins without Affecting Live Site\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Edit wp-config.php constants\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Read debug.log file\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Security Mode if site is broken\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>How to use it?\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>1. Remote Access – Login without password\u003C\u002Fstrong>\u003Cbr \u002F>\n=> When any support member asked you for login details. You can provide them this URL. The support team can log in through that URL. No need of any email and password. Safe and Secure. All administrator access but they cannot change the user role of any user.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>2. Troubleshoot Theme and Plugins without Affecting Live Site\u003C\u002Fstrong>\u003Cbr \u002F>\n=> Sometimes you need to deactivate a plugin on live site to find a conflict. support team member always asks this permission to activate\u002Fdeactivate plugins. Here is a solution. This plugin will deactivate plugins and themes just for the current login user. Go To \u003Cstrong>Settings->Geeky Troubleshooter->Troubleshoot Theme & Plugins\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>3. Edit wp-config.php constants\u003C\u002Fstrong>\u003Cbr \u002F>\n=> You can edit wp-config file constants. No need of FTP.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>4. Debug File Reader\u003C\u002Fstrong>\u003Cbr \u002F>\n=> Read debug log file from your dashboard.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>5. Security Mode if the site is broken\u003C\u002Fstrong>\u003Cbr \u002F>\n=> This is one of the amazing feature ever. What if your site broke due to a recently activated plugin. Go To \u003Cstrong>Settings->Geeky Troubleshooter->Secuirty Code.\u003C\u002Fstrong>. It is like a password. It will deactivate all the plugins just for you except WP Geeky Troubleshooter. You just need to enter the security code in URL \u003Cstrong>example.com?wgs_security_code=your_code\u003C\u002Fstrong> then log in with your login details. It will open security mode. Select the required plugin. That’s it. Exit the security mode. Your site is back.\u003C\u002Fp>\n","Easily Troubleshoot Your WordPress Site wihout Affecting Live Site.",10,1125,0,"2019-04-06T09:07:00.000Z","5.1.22","4.4","5.6",[19,20],"troubleshoot","wsod","https:\u002F\u002Fwww.techiesandesh.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-geeky-troubleshooter.1.0.0.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":28,"display_name":7,"profile_url":8,"plugin_count":29,"total_installs":30,"avg_security_score":23,"avg_patch_time_days":31,"trust_score":32,"computed_at":33},"sandesh055",6,740,30,84,"2026-04-04T18:45:16.046Z",[35,59,82,104,124],{"slug":36,"name":37,"version":38,"author":39,"author_profile":40,"description":41,"short_description":42,"active_installs":43,"downloaded":44,"rating":45,"num_ratings":46,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":50,"tags":51,"homepage":56,"download_link":57,"security_score":58,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25},"plugin-detective","Plugin Detective – Troubleshooting Conflicts","1.2.29","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","Plugin Detective helps you troubleshoot issues on your site quickly and easily to find the cause of a problem. Once the culprit is found, the problem  …",5000,211383,80,48,"2025-12-09T17:11:00.000Z","6.9.4","6.1","5.3",[52,53,54,55,19],"administration","conflicts","debug","support","https:\u002F\u002Fnsquared.io","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fplugin-detective.1.2.29.zip",100,{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":69,"num_ratings":70,"last_updated":71,"tested_up_to":72,"requires_at_least":73,"requires_php":74,"tags":75,"homepage":80,"download_link":81,"security_score":58,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25},"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,24163,86,8,"2025-04-23T09:57:00.000Z","6.8.5","4.6","5.2.6",[54,76,77,78,79],"debugging","recovery","safe-mode","troubleshooting","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-safe-mode\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-safe-mode.1.3.zip",{"slug":83,"name":84,"version":85,"author":86,"author_profile":87,"description":88,"short_description":89,"active_installs":90,"downloaded":91,"rating":58,"num_ratings":92,"last_updated":93,"tested_up_to":94,"requires_at_least":95,"requires_php":96,"tags":97,"homepage":101,"download_link":102,"security_score":103,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25},"wp-mail-debugger","WP Mail Debugger","1.1","Timothy Jacobs","https:\u002F\u002Fprofiles.wordpress.org\u002Ftimothyblynjacobs\u002F","\u003Cp>WP Mail Debugger captures and displays all emails sent through wp_mail() for debugging and troubleshooting. A new admin menu, WP Mail Debugger, is added under the Tools menu.\u003C\u002Fp>\n\u003Cp>Get the \u003Ca href=\"https:\u002F\u002Fapps.apple.com\u002Fus\u002Fapp\u002Fwp-mail-debugger\u002Fid1547093438?mt=12\" rel=\"nofollow ugc\">Mac App\u003C\u002Fa> to connect to multiple WordPress websites from one convenient location.\u003C\u002Fp>\n","WP Mail Debugger captures and displays all emails sent through wp_mail() for debugging and troubleshooting.",300,9000,2,"2024-07-22T02:23:00.000Z","6.6.5","6.3.0","7.2.0",[54,98,99,79,100],"email","email-log","wp-mail","https:\u002F\u002Fwpmaildebugger.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-mail-debugger.1.1.zip",92,{"slug":105,"name":106,"version":107,"author":108,"author_profile":109,"description":110,"short_description":111,"active_installs":58,"downloaded":112,"rating":113,"num_ratings":114,"last_updated":115,"tested_up_to":48,"requires_at_least":116,"requires_php":17,"tags":117,"homepage":122,"download_link":123,"security_score":58,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25},"conflict-finder-wp-fix-it","Conflict Finder","7.2","WP Fix It - WordPress Experts","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpfixit\u002F","\u003Cp>Conflict Finder is a comprehensive troubleshooting plugin designed for WordPress administrators, developers, and support professionals who need to identify the root cause of site issues.\u003C\u002Fp>\n\u003Cp>From a single interface, Conflict Finder allows you to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enable and manage WP_DEBUG without manually editing files\u003C\u002Fli>\n\u003Cli>View, download, and clear the WordPress debug log\u003C\u002Fli>\n\u003Cli>Temporarily disable plugins to identify conflicts\u003C\u002Fli>\n\u003Cli>Switch themes to test theme-related issues\u003C\u002Fli>\n\u003Cli>Test WordPress email delivery using \u003Ccode>wp_mail()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Important:\u003C\u002Fstrong>\u003Cbr \u002F>\nConflict Finder \u003Cstrong>does temporarily affect site behavior\u003C\u002Fstrong> while troubleshooting is active. This may include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Disabled plugins\u003C\u002Fli>\n\u003Cli>A different active theme\u003C\u002Fli>\n\u003Cli>Debug notices or errors being displayed\u003C\u002Fli>\n\u003Cli>Changes visible to logged-out visitors\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For this reason, troubleshooting should be performed during maintenance windows or on staging sites whenever possible.\u003C\u002Fp>\n\u003Cp>Conflict Finder automatically tracks your original configuration and allows you to restore plugins, themes, and debugging settings once testing is complete.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Troubleshooting Dashboard\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Central overview of debugging and conflict states\u003C\u002Fli>\n\u003Cli>Environment snapshot including WordPress, PHP, memory, and server software\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>WP_DEBUG Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enable or disable WP_DEBUG with a single switch\u003C\u002Fli>\n\u003Cli>Control error display and logging behavior\u003C\u002Fli>\n\u003Cli>Load unminified scripts for debugging\u003C\u002Fli>\n\u003Cli>View, download, or clear \u003Ccode>wp-content\u002Fdebug.log\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Safely updates \u003Ccode>wp-config.php\u003C\u002Fcode> as needed\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Plugin Conflict Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Temporarily deactivate all active plugins\u003C\u002Fli>\n\u003Cli>Save and restore original plugin states\u003C\u002Fli>\n\u003Cli>Activate plugins one at a time to identify conflicts\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Theme Conflict Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Temporarily switch to another installed theme\u003C\u002Fli>\n\u003Cli>Identify theme-related layout or functionality issues\u003C\u002Fli>\n\u003Cli>Restore the original theme instantly\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Email Delivery Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Send a real test email using WordPress mail\u003C\u002Fli>\n\u003Cli>Confirm whether the server can successfully send email\u003C\u002Fli>\n\u003Cli>Helps identify SMTP or hosting mail issues\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>When to Use Conflict Finder\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Diagnosing white screens or fatal errors\u003C\u002Fli>\n\u003Cli>Identifying plugin conflicts\u003C\u002Fli>\n\u003Cli>Testing theme-related layout or functionality issues\u003C\u002Fli>\n\u003Cli>Investigating PHP notices or warnings\u003C\u002Fli>\n\u003Cli>Verifying WordPress email delivery\u003C\u002Fli>\n\u003Cli>Support and development workflows\u003C\u002Fli>\n\u003C\u002Ful>\n","Conflict Finder is a WordPress troubleshooting toolkit that helps diagnose plugin conflicts, theme issues, debugging errors, and email delivery proble …",8747,90,4,"2026-01-27T14:26:00.000Z","4.9",[118,119,120,79,121],"debug-log","plugin-conflict","theme-conflict","wp_debug","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fconflict-finder-wp-fix-it.7.2.zip",{"slug":125,"name":126,"version":85,"author":127,"author_profile":128,"description":129,"short_description":130,"active_installs":58,"downloaded":131,"rating":132,"num_ratings":92,"last_updated":133,"tested_up_to":134,"requires_at_least":135,"requires_php":122,"tags":136,"homepage":139,"download_link":140,"security_score":23,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25},"phpinfo","Phpinfo","Roland Rust","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpdprx\u002F","\u003Cp>Prints out your webservers php settings as well as other information about your WordPress installation.\u003Cbr \u002F>\nImportant for posting at various WordPress support forums.\u003C\u002Fp>\n","Prints out your webservers php settings as well as other information about your WordPress installation.",16305,70,"2007-09-14T07:38:00.000Z","2.2.2","1.5",[137,76,125,138,79],"configuration","server","http:\u002F\u002Fwordpress.designpraxis.at","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fphpinfo.zip",{"attackSurface":142,"codeSignals":219,"taintFlows":251,"riskAssessment":314,"analyzedAt":321},{"hooks":143,"ajaxHandlers":198,"restRoutes":216,"shortcodes":217,"cronEvents":218,"entryPointCount":114,"unprotectedCount":13},[144,151,156,160,164,169,173,179,183,187,191,194,196],{"type":145,"name":146,"callback":147,"priority":148,"file":149,"line":150},"action","admin_menu","submenu",999,"support-core\\class-gs-admin.php",59,{"type":145,"name":152,"callback":153,"priority":154,"file":149,"line":155},"init","save_settings_and_scripts",20,61,{"type":145,"name":157,"callback":158,"file":149,"line":159},"admin_enqueue_scripts","styles_scripts",114,{"type":145,"name":152,"callback":161,"file":162,"line":163},"init_login","support-core\\class-gs-front.php",72,{"type":165,"name":166,"callback":167,"priority":148,"file":162,"line":168},"filter","template","troubleshoot_template",242,{"type":165,"name":170,"callback":171,"priority":148,"file":162,"line":172},"stylesheet","troubleshoot_stylesheet",243,{"type":145,"name":174,"callback":175,"priority":176,"file":177,"line":178},"plugins_loaded","load_plugin",99,"support-core\\class-gs-loader.php",64,{"type":145,"name":146,"callback":180,"file":181,"line":182},"admin_menus","support-core\\class-gs-security-mode.php",49,{"type":145,"name":184,"callback":185,"file":181,"line":186},"admin_init","setup_wizard",50,{"type":165,"name":188,"callback":189,"file":181,"line":190},"option_active_plugins","troubleshoot_mode_disable_plugins",277,{"type":165,"name":192,"callback":189,"file":181,"line":193},"option_active_sitewide_plugins",278,{"type":165,"name":188,"callback":189,"file":195,"line":155},"support-core\\mu-plugins\\class-gs-mu-plugin.php",{"type":165,"name":192,"callback":189,"file":195,"line":197},62,[199,205,208,212],{"action":200,"nopriv":201,"callback":202,"hasNonce":203,"hasCapCheck":203,"file":149,"line":204},"wgs_save_remote_access",false,"save_remote_access",true,63,{"action":206,"nopriv":201,"callback":207,"hasNonce":203,"hasCapCheck":203,"file":149,"line":178},"wgs_regenerate_login_link","regenerate_login_link",{"action":209,"nopriv":201,"callback":210,"hasNonce":203,"hasCapCheck":201,"file":149,"line":211},"wgs_save_troubleshoot_mode","save_troubleshoot_mode",66,{"action":213,"nopriv":201,"callback":214,"hasNonce":203,"hasCapCheck":201,"file":149,"line":215},"wgs_save_security_code","save_security_code",68,[],[],[],{"dangerousFunctions":220,"sqlUsage":221,"outputEscaping":223,"fileOperations":248,"externalRequests":13,"nonceChecks":248,"capabilityChecks":249,"bundledLibraries":250},[],{"prepared":114,"raw":13,"locations":222},[],{"escaped":224,"rawEcho":11,"locations":225},34,[226,230,232,234,235,237,240,242,244,246],{"file":227,"line":228,"context":229},"support-core\\admin\\view\\support-data.php",35,"raw output",{"file":227,"line":231,"context":229},45,{"file":227,"line":233,"context":229},54,{"file":227,"line":132,"context":229},{"file":227,"line":236,"context":229},79,{"file":238,"line":239,"context":229},"support-core\\class-gs-admin-data.php",492,{"file":181,"line":241,"context":229},195,{"file":181,"line":243,"context":229},217,{"file":181,"line":245,"context":229},219,{"file":181,"line":247,"context":229},306,7,3,[],[252,270,283,296,306],{"entryPoint":253,"graph":254,"unsanitizedCount":13,"severity":269},"save_config_constants (support-core\\class-gs-admin.php:164)",{"nodes":255,"edges":267},[256,261],{"id":257,"type":258,"label":259,"file":149,"line":260},"n0","source","$_SERVER",190,{"id":262,"type":263,"label":264,"file":149,"line":265,"wp_function":266},"n1","sink","wp_redirect() [Open Redirect]",197,"wp_redirect",[268],{"from":257,"to":262,"sanitized":203},"low",{"entryPoint":271,"graph":272,"unsanitizedCount":13,"severity":269},"save_security_code (support-core\\class-gs-admin.php:393)",{"nodes":273,"edges":281},[274,277],{"id":257,"type":258,"label":275,"file":149,"line":276},"$_POST",397,{"id":262,"type":263,"label":278,"file":149,"line":279,"wp_function":280},"update_option() [Settings Manipulation]",412,"update_option",[282],{"from":257,"to":262,"sanitized":203},{"entryPoint":284,"graph":285,"unsanitizedCount":13,"severity":269},"\u003Cclass-gs-admin> (support-core\\class-gs-admin.php:0)",{"nodes":286,"edges":293},[287,288,289,291],{"id":257,"type":258,"label":259,"file":149,"line":260},{"id":262,"type":263,"label":264,"file":149,"line":265,"wp_function":266},{"id":290,"type":258,"label":275,"file":149,"line":276},"n2",{"id":292,"type":263,"label":278,"file":149,"line":279,"wp_function":280},"n3",[294,295],{"from":257,"to":262,"sanitized":203},{"from":290,"to":292,"sanitized":203},{"entryPoint":297,"graph":298,"unsanitizedCount":13,"severity":269},"plugin_updates_save (support-core\\class-gs-security-mode.php:324)",{"nodes":299,"edges":304},[300,302],{"id":257,"type":258,"label":275,"file":181,"line":301},334,{"id":262,"type":263,"label":278,"file":181,"line":303,"wp_function":280},339,[305],{"from":257,"to":262,"sanitized":203},{"entryPoint":307,"graph":308,"unsanitizedCount":13,"severity":269},"\u003Cclass-gs-security-mode> (support-core\\class-gs-security-mode.php:0)",{"nodes":309,"edges":312},[310,311],{"id":257,"type":258,"label":275,"file":181,"line":301},{"id":262,"type":263,"label":278,"file":181,"line":303,"wp_function":280},[313],{"from":257,"to":262,"sanitized":203},{"summary":315,"deductions":316},"The wp-geeky-troubleshooter plugin v1.0.0 exhibits a generally good security posture based on the provided static analysis. The absence of any known CVEs, unpatched vulnerabilities, or vulnerabilities of any severity in its history is a significant strength. Furthermore, the code analysis reveals no critical or high severity taint flows, no raw SQL queries, and a substantial number of nonce and capability checks, indicating an effort to implement secure coding practices. The lack of external HTTP requests also reduces the attack surface.\n\nHowever, there are areas for improvement. While the number of unprotected entry points is zero, 4 AJAX handlers represent potential entry points that, while currently protected by checks (as implied by the 0 unprotected count), would be a higher risk if those checks were ever bypassed or found insufficient. The output escaping, while 77% proper, still leaves a portion of outputs unescaped, which could lead to Cross-Site Scripting (XSS) vulnerabilities if untrusted data is involved in those specific outputs. The presence of file operations, while not inherently insecure, requires careful scrutiny in the context of the plugin's functionality to ensure they are not susceptible to arbitrary file read\u002Fwrite vulnerabilities.\n\nOverall, the plugin's security history is excellent, and the static analysis shows a solid foundation. The main potential risks lie in the remaining unescaped outputs and the inherent nature of AJAX handlers as potential attack vectors that need continuous vigilance. The absence of known vulnerabilities suggests that the developers have been diligent, but the remaining code signals warrant attention for a truly robust security profile.",[317,319],{"reason":318,"points":29},"Unescaped output identified",{"reason":320,"points":249},"Potential risk in AJAX handlers (no explicit auth bypass found)","2026-03-17T00:47:17.642Z",{"wat":323,"direct":332},{"assetPaths":324,"generatorPatterns":327,"scriptPaths":328,"versionParams":329},[325,326],"\u002Fwp-content\u002Fplugins\u002Fwp-geeky-troubleshooter\u002Fcss\u002Fsupport-center.css","\u002Fwp-content\u002Fplugins\u002Fwp-geeky-troubleshooter\u002Fjs\u002Fsupport-center.js",[],[326],[330,331],"wp-geeky-troubleshooter\u002Fcss\u002Fsupport-center.css?ver=","wp-geeky-troubleshooter\u002Fjs\u002Fsupport-center.js?ver=",{"cssClasses":333,"htmlComments":335,"htmlAttributes":336,"restEndpoints":338,"jsGlobals":340,"shortcodeOutput":342},[334],"geeky-support-admin",[],[337],"data-nonce",[339],"\u002Fwp-json\u002Fwgs\u002F",[341],"geeky_support",[]]