[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fxWUl7dbEBiCmUoL0Hf7GIpXC0cJOf93gOKRcSfKU_gY":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":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":24,"download_link":25,"security_score":26,"vuln_count":14,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29,"vulnerabilities":30,"developer":46,"crawl_stats":36,"alternatives":50,"analysis":148,"fingerprints":333},"debugger-troubleshooter","Debugger & Troubleshooter","1.3.2","Jhimross Olinares","https:\u002F\u002Fprofiles.wordpress.org\u002Fjhimross\u002F","\u003Cp>The “Debugger & Troubleshooter” plugin provides essential tools for WordPress site administrators to diagnose and resolve issues efficiently. It offers a dedicated section in the WordPress dashboard that displays comprehensive site health information and powerful debugging toggles.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Key Features:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Troubleshooting Mode:\u003C\u002Fstrong> Activate a unique, \u003Cstrong>session-based\u003C\u002Fstrong> “Troubleshooting Mode” for your current browser session. This means any changes you make are temporary and only visible to you. This mode allows you to:\n\u003Cul>\n\u003Cli>\u003Cstrong>Simulate Plugin Deactivation:\u003C\u002Fstrong> Selectively “deactivate” plugins. The plugin’s assets and code will be disabled for your session only.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Simulate Theme Switching:\u003C\u002Fstrong> Preview any installed theme, while the public-facing site continues to use the active theme.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>User Role Simulator:\u003C\u002Fstrong> View your site as any other user or role (e.g., Subscriber, Editor) to test permissions and content visibility. This is session-based and includes a safe “Exit” button in the Admin Bar.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Live Debugging:\u003C\u002Fstrong> Safely enable \u003Ccode>WP_DEBUG\u003C\u002Fcode> with a single click from the admin dashboard. Errors are logged to \u003Ccode>debug.log\u003C\u002Fcode> without being displayed on the site, and you can view the log file directly in the plugin’s interface.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Comprehensive Site Information:\u003C\u002Fstrong> Get a quick, organized overview of your WordPress environment in collapsible cards. This includes detailed PHP, Database, and Server information, a full list of all themes and plugins with their status, and important WordPress constants.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Copy to Clipboard:\u003C\u002Fstrong> A one-click button allows you to copy all the site information, making it incredibly easy to share with support forums or developers.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Safe Debugging & Cache Bypassing:\u003C\u002Fstrong> All troubleshooting actions are session-based. The plugin automatically attempts to bypass caching when Troubleshooting Mode is active, ensuring your changes are reflected instantly.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>User-Friendly Interface:\u003C\u002Fstrong> An intuitive dashboard interface makes it easy to access all features.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Admin Notices:\u003C\u002Fstrong> Clear notices alert you when Troubleshooting Mode is active.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This plugin is an invaluable tool for developers, site administrators, and anyone who needs to debug WordPress issues without risking site downtime or affecting user experience.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>Once the plugin is installed and activated, navigate to \u003Cstrong>Tools > Debugger & Troubleshooter\u003C\u002Fstrong> in your WordPress dashboard.\u003C\u002Fp>\n\u003Ch3>1. Site Information\u003C\u002Fh3>\n\u003Cp>The top section provides a comprehensive overview of your WordPress environment, organized into collapsible cards that are closed by default. Click on any card title to expand it and view the details.\u003C\u002Fp>\n\u003Ch3>2. Troubleshooting Mode\u003C\u002Fh3>\n\u003Cp>This session-based feature allows you to simulate theme switches and plugin deactivations without affecting your live website for other visitors.\u003C\u002Fp>\n\u003Ch3>3. User Role Simulator\u003C\u002Fh3>\n\u003Cp>Safely view your site as another user or role (e.g., “Subscriber” or “Editor”) without knowing their password. This is perfect for testing capabilities and content restrictions.\u003C\u002Fp>\n\u003Ch3>4. Live Debugging\u003C\u002Fh3>\n\u003Cp>This section allows you to safely manage WordPress’s debugging features.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Enable Live Debug:\u003C\u002Fstrong> Click this button to programmatically enable \u003Ccode>WP_DEBUG\u003C\u002Fcode> and \u003Ccode>WP_DEBUG_LOG\u003C\u002Fcode>, while keeping \u003Ccode>WP_DEBUG_DISPLAY\u003C\u002Fcode> off. This logs errors to \u003Ccode>wp-content\u002Fdebug.log\u003C\u002Fcode> without showing them to visitors.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debug Log Viewer:\u003C\u002Fstrong> A text area displays the contents of your \u003Ccode>debug.log\u003C\u002Fcode> file, allowing you to see errors as they are generated.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Clear Log:\u003C\u002Fstrong> Safely clear the \u003Ccode>debug.log\u003C\u002Fcode> file with a click.\u003C\u002Fli>\n\u003C\u002Ful>\n","A WordPress plugin for debugging & troubleshooting. Safely simulate plugin deactivation, theme switching, and WP_DEBUG.",40,812,100,1,"2026-02-11T15:40:00.000Z","6.8.5","5.0","7.4",[20,21,22,23],"debug","developer","php-info","troubleshoot","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebugger-troubleshooter","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebugger-troubleshooter.1.3.2.zip",97,0,"2026-03-30 09:30:13","2026-03-15T15:16:48.613Z",[31],{"id":32,"url_slug":33,"title":34,"description":35,"plugin_slug":4,"theme_slug":36,"affected_versions":37,"patched_in_version":38,"severity":39,"cvss_score":40,"cvss_vector":41,"vuln_type":42,"published_date":28,"updated_date":43,"references":44,"days_to_patch":14},"CVE-2026-5130","debugger-troubleshooter-unauthenticated-privilege-escalation-to-administrator-via-cookie-manipulation","Debugger & Troubleshooter \u003C= 1.3.2 - Unauthenticated Privilege Escalation to Administrator via Cookie Manipulation","The Debugger & Troubleshooter plugin for WordPress was vulnerable to Unauthenticated Privilege Escalation in versions up to and including 1.3.2. This was due to the plugin accepting the wp_debug_troubleshoot_simulate_user cookie value directly as a user ID without any cryptographic validation or authorization checks. The cookie value was used to override the determine_current_user filter, which allowed unauthenticated attackers to impersonate any user by simply setting the cookie to their target user ID. This made it possible for unauthenticated attackers to gain administrator-level access and perform any privileged actions including creating new administrator accounts, modifying site content, installing plugins, or taking complete control of the WordPress site. The vulnerability was fixed in version 1.4.0 by implementing a cryptographic token-based validation system where only administrators can initiate user simulation, and the cookie contains a random 64-character token that must be validated against database-stored mappings rather than accepting arbitrary user IDs.",null,"\u003C=1.3.2","1.4.0","high",8.8,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:U\u002FC:H\u002FI:H\u002FA:H","Reliance on Cookies without Validation and Integrity Checking","2026-03-30 22:24:59",[45],"https:\u002F\u002Fwww.wordfence.com\u002Fthreat-intel\u002Fvulnerabilities\u002Fid\u002F3e037931-870f-45eb-973c-0276911682ad?source=api-prod",{"slug":47,"display_name":7,"profile_url":8,"plugin_count":14,"total_installs":11,"avg_security_score":26,"avg_patch_time_days":14,"trust_score":48,"computed_at":49},"jhimross",98,"2026-04-05T02:30:40.602Z",[51,70,86,107,128],{"slug":52,"name":53,"version":54,"author":55,"author_profile":56,"description":57,"short_description":58,"active_installs":27,"downloaded":59,"rating":13,"num_ratings":14,"last_updated":60,"tested_up_to":61,"requires_at_least":17,"requires_php":62,"tags":63,"homepage":68,"download_link":69,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":36,"fetched_at":29},"developer-debug-mode","Developer Debug Mode","1.2.5","Glimbyte","https:\u002F\u002Fprofiles.wordpress.org\u002Fglimbyte\u002F","\u003Cp>\u003Cstrong>Stop editing wp-config.php every time you need to debug your WordPress site.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Developer Debug Mode lets you toggle all WordPress debug constants directly from your dashboard with beautiful toggle switches. Changes save automatically — no clicking save buttons, no FTP access needed, no risk of syntax errors in your config file.\u003C\u002Fp>\n\u003Ch4>🎯 The Problem This Plugin Solves\u003C\u002Fh4>\n\u003Cp>Every WordPress developer knows the pain:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Something breaks on your site\u003C\u002Fli>\n\u003Cli>You need to enable WP_DEBUG to see the error\u003C\u002Fli>\n\u003Cli>You open FTP\u002FFile Manager, find wp-config.php, edit it carefully\u003C\u002Fli>\n\u003Cli>Debug the issue\u003C\u002Fli>\n\u003Cli>Remember to turn debug off before visitors see ugly error messages\u003C\u002Fli>\n\u003Cli>Repeat next time something breaks\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Developer Debug Mode eliminates steps 2-5 entirely.\u003C\u002Fstrong> Toggle debug on, find the error, toggle off. Done in seconds.\u003C\u002Fp>\n\u003Ch4>✨ Key Features\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>One-Click Debug Toggles\u003C\u002Fstrong>\u003Cbr \u002F>\nControl all six WordPress debug constants from a clean, modern interface:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>WP_DEBUG\u003C\u002Fstrong> — Master switch for WordPress debugging\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DEBUG_LOG\u003C\u002Fstrong> — Save errors to wp-content\u002Fdebug.log\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DEBUG_DISPLAY\u003C\u002Fstrong> — Show errors on screen (careful on production!)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SCRIPT_DEBUG\u003C\u002Fstrong> — Use unminified core CSS\u002FJS files\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SAVEQUERIES\u003C\u002Fstrong> — Log database queries for performance analysis\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DISABLE_FATAL_ERROR_HANDLER\u003C\u002Fstrong> — See raw PHP fatal errors instead of recovery mode\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Admin Bar Quick Toggle\u003C\u002Fstrong> \u003Cem>(New in 1.2.0!)\u003C\u002Fem>\u003Cbr \u002F>\nToggle any debug constant directly from the WordPress admin bar — no need to visit the settings page. Perfect for quick debugging sessions.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Built-in Debug Log Viewer\u003C\u002Fstrong>\u003Cbr \u002F>\nView, search, download, and clear your debug.log without leaving WordPress:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Color-coded entries (fatal, error, warning, notice)\u003C\u002Fli>\n\u003Cli>Search with highlighting\u003C\u002Fli>\n\u003Cli>Auto-refresh option for real-time monitoring\u003C\u002Fli>\n\u003Cli>One-click download and clear\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Auto-Save Technology\u003C\u002Fstrong>\u003Cbr \u002F>\nChanges save instantly as you toggle. No save button, no page refresh, no waiting.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Frontend Debug Warning\u003C\u002Fstrong>\u003Cbr \u002F>\nA tasteful notification bar appears when WP_DEBUG_DISPLAY is active, reminding you to turn it off before visitors see error messages.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Cross-Tab Synchronization\u003C\u002Fstrong>\u003Cbr \u002F>\nToggle debug in one browser tab and watch other open tabs update instantly.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Automatic Backups\u003C\u002Fstrong>\u003Cbr \u002F>\nEvery change creates a backup of wp-config.php. The plugin keeps the 5 most recent backups, so you can always recover if something goes wrong.\u003C\u002Fp>\n\u003Ch4>🔧 Perfect For\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Theme developers\u003C\u002Fstrong> debugging template issues\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Plugin developers\u003C\u002Fstrong> testing new code\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Site administrators\u003C\u002Fstrong> troubleshooting problems\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Agencies\u003C\u002Fstrong> managing multiple client sites\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Freelancers\u003C\u002Fstrong> who need quick debugging without FTP access\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Anyone\u003C\u002Fstrong> tired of manually editing wp-config.php\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>💡 Why Choose Developer Debug Mode?\u003C\u002Fh4>\n\u003Cp>Unlike other debug plugins, we focus on \u003Cstrong>user experience\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cp>✅ \u003Cstrong>Instant toggles\u003C\u002Fstrong> — No save buttons, changes apply immediately\u003Cbr \u002F>\n✅ \u003Cstrong>Visual feedback\u003C\u002Fstrong> — Clear status indicators show exactly what’s enabled\u003Cbr \u002F>\n✅ \u003Cstrong>Admin bar access\u003C\u002Fstrong> — Toggle debug from anywhere in WordPress\u003Cbr \u002F>\n✅ \u003Cstrong>Production-safe\u003C\u002Fstrong> — Frontend warnings prevent accidentally exposing errors\u003Cbr \u002F>\n✅ \u003Cstrong>Modern design\u003C\u002Fstrong> — Beautiful UI that fits naturally in your dashboard\u003Cbr \u002F>\n✅ \u003Cstrong>Lightweight\u003C\u002Fstrong> — No bloat, loads only where needed\u003C\u002Fp>\n\u003Ch4>🔒 Built With Security In Mind\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Capability checks ensure only administrators can change settings\u003C\u002Fli>\n\u003Cli>Nonce verification on all AJAX requests\u003C\u002Fli>\n\u003Cli>Automatic wp-config.php backups before every change\u003C\u002Fli>\n\u003Cli>No data sent to external servers\u003C\u002Fli>\n\u003Cli>Clean uninstall removes all plugin data\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>📚 Debug Constants Explained\u003C\u002Fh4>\n\u003Cp>Not sure what each constant does? Here’s a quick guide:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP_DEBUG\u003C\u002Fstrong>\u003Cbr \u002F>\nThe master switch. When enabled, WordPress will display PHP errors, notices, and warnings. Required for the other debug constants to work.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP_DEBUG_LOG\u003C\u002Fstrong>\u003Cbr \u002F>\nSaves all debug messages to \u003Ccode>\u002Fwp-content\u002Fdebug.log\u003C\u002Fcode>. Essential for debugging issues that happen in the background (AJAX, cron jobs, REST API).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP_DEBUG_DISPLAY\u003C\u002Fstrong>\u003Cbr \u002F>\nShows errors directly on your web pages. Useful during development but \u003Cstrong>never enable on production\u003C\u002Fstrong> — it can expose sensitive information to visitors.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>SCRIPT_DEBUG\u003C\u002Fstrong>\u003Cbr \u002F>\nForces WordPress to use the development versions of core CSS and JavaScript files instead of minified versions. Helpful when debugging scripts.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>SAVEQUERIES\u003C\u002Fstrong>\u003Cbr \u002F>\nStores database queries in a global array for later analysis. Useful for identifying slow queries but adds overhead — disable when not needed.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WP_DISABLE_FATAL_ERROR_HANDLER\u003C\u002Fstrong>\u003Cbr \u002F>\nDisables WordPress’s “recovery mode” so you see the actual PHP fatal error instead of “There has been a critical error on this website.”\u003C\u002Fp>\n\u003Ch4>🤝 Support & Documentation\u003C\u002Fh4>\n\u003Cp>Need help? We offer:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Free Support\u003C\u002Fstrong> — Post in the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fdeveloper-debug-mode\u002F\" rel=\"ugc\">WordPress.org support forum\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Documentation\u003C\u002Fstrong> — Visit \u003Ca href=\"https:\u002F\u002Fglimbyte.ie\" rel=\"nofollow ugc\">glimbyte.ie\u003C\u002Fa> for guides and tutorials\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Express Support\u003C\u002Fstrong> — Fast turnaround for urgent issues via \u003Ca href=\"https:\u002F\u002Fglimbyte.ie\u002Fsupport\" rel=\"nofollow ugc\">glimbyte.ie\u002Fsupport\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>🌐 Works Great With\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Query Monitor\u003C\u002Fstrong> — Use alongside for deeper debugging\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debug Bar\u003C\u002Fstrong> — Compatible with Debug Bar and its add-ons\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Any caching plugin\u003C\u002Fstrong> — Clear cache after toggling debug constants\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Managed WordPress hosts\u003C\u002Fstrong> — Works on most hosts including Kinsta, WP Engine, SiteGround\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cp>Developed with ❤️ by \u003Ca href=\"https:\u002F\u002Fglimbyte.ie\" rel=\"nofollow ugc\">Glimbyte\u003C\u002Fa> — WordPress Development & Support.\u003C\u002Fp>\n\u003Cp>Special thanks to the WordPress community for feedback and suggestions.\u003C\u002Fp>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>Developer Debug Mode does not collect, store, or transmit any personal data. All settings are stored locally in your WordPress database and wp-config.php file.\u003C\u002Fp>\n\u003Cp>The optional support contact form (available in the plugin settings) sends data directly to Glimbyte’s support team. This data is handled according to \u003Ca href=\"https:\u002F\u002Fglimbyte.ie\u002Fprivacy\" rel=\"nofollow ugc\">Glimbyte’s Privacy Policy\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Additional Info\u003C\u002Fh3>\n\u003Ch4>Contribute\u003C\u002Fh4>\n\u003Cp>Found a bug or have a feature request? We’d love to hear from you!\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Support Forum:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fdeveloper-debug-mode\u002F\" rel=\"ugc\">wordpress.org\u002Fsupport\u002Fplugin\u002Fdeveloper-debug-mode\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Website:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fglimbyte.ie\" rel=\"nofollow ugc\">glimbyte.ie\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Translations\u003C\u002Fh4>\n\u003Cp>Want to help translate Developer Debug Mode into your language? Visit \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fdeveloper-debug-mode\u002F\" rel=\"nofollow ugc\">translate.wordpress.org\u003C\u002Fa> to contribute.\u003C\u002Fp>\n","Toggle WordPress debug mode instantly. No wp-config.php editing needed. Features auto-save, admin bar quick toggle, and debug log viewer.",105,"2026-02-06T13:02:00.000Z","6.9.4","7.0",[20,64,65,66,67],"developer-tools","error-log","troubleshooting","wp-config","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdeveloper-debug-mode.1.2.5.zip",{"slug":71,"name":72,"version":73,"author":74,"author_profile":75,"description":76,"short_description":77,"active_installs":27,"downloaded":78,"rating":27,"num_ratings":27,"last_updated":79,"tested_up_to":16,"requires_at_least":17,"requires_php":80,"tags":81,"homepage":84,"download_link":85,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":36,"fetched_at":29},"notice-trace-log","Notice TraceLog","1.1.0","shuliakmaster","https:\u002F\u002Fprofiles.wordpress.org\u002Fshuliakmaster\u002F","\u003Cp>Notice TraceLog is a lightweight developer tool that displays PHP backtraces when Notices occur, helping you identify and fix issues caused by early execution or translation loading problems. Useful for debugging during plugin and theme development.\u003C\u002Fp>\n","Easily display PHP backtraces when Notices occur. Designed for developers to quickly identify the source of early execution issues in WordPress.",355,"2025-06-25T12:45:00.000Z","7.2",[82,20,21,83,66],"backtrace","notices","https:\u002F\u002Fgithub.com\u002Fupandrii\u002Fdebug-backtrace","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnotice-trace-log.1.1.0.zip",{"slug":87,"name":88,"version":89,"author":90,"author_profile":91,"description":92,"short_description":93,"active_installs":94,"downloaded":95,"rating":13,"num_ratings":96,"last_updated":97,"tested_up_to":16,"requires_at_least":98,"requires_php":99,"tags":100,"homepage":102,"download_link":103,"security_score":104,"vuln_count":105,"unpatched_count":27,"last_vuln_date":106,"fetched_at":29},"debug-log-manager","Debug Log Manager – Conveniently Monitor and Inspect Errors","2.4.3","Bowo","https:\u002F\u002Fprofiles.wordpress.org\u002Fqriouslad\u002F","\u003Cp>Debug Log Manager allows you to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Enable \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Farticle\u002Fdebugging-in-wordpress\u002F\" rel=\"ugc\">WP_DEBUG\u003C\u002Fa> with one click to log PHP, database and JavaScript errors\u003C\u002Fstrong> when you need to, and disable it when you’re done. No need to manually edit wp-config.php file. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Create the debug.log file for you\u003C\u002Fstrong> in a non-default location with a custom file name for enhanced security. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Copy the content of the default \u002F existing debug.log file\u003C\u002Fstrong> into the custom debug.log file, and delete the default \u002F existing debug.log file. So there is continuation in logging and enhanced security going forward.\u003C\u002Fli>\n\u003Cli>Parse the debug.log file and \u003Cstrong>view distinct errors and when they last occurred\u003C\u002Fstrong>, which is better than looking at the raw log file (potentially) full of repetitive errors. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Quickly find and filter more specific errors\u003C\u002Fstrong> for your debugging work.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Make error details easier to read\u003C\u002Fstrong> by identifying error source (core \u002F plugin \u002F theme) and separating file path and line number.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Easily view files where PHP errors occurred\u003C\u002Fstrong>. This includes WordPress core, plugin and theme files.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enable auto-refresh\u003C\u002Fstrong> to automatically load new log entries. No need to manually reload the browser tab, or to \u003Ccode>tail -f\u003C\u002Fcode> the log file on the command line.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Easily clear the debug.log file\u003C\u002Fstrong> to save disk space and more easily observe newly occurring errors on your site.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Show an indicator on the admin bar\u003C\u002Fstrong> when error logging is enabled.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Add a dashboard widget\u003C\u002Fstrong> showing the latest errors logged.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Use \u003Ccode>error_log()\u003C\u002Fcode>\u003C\u002Fstrong> to output error info into your debug log. e.g. \u003Ccode>error_log( $error_message )\u003C\u002Fcode> for simple, string-based error message, or \u003Ccode>error_log( json_encode( $error ) )\u003C\u002Fcode> when inspecting a more complex error info, e.g. array or object.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A simpler and more compact version of Debug Log Manager is included as part of the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsystem-dashboard\u002F\" rel=\"ugc\">System Dashboard plugin\u003C\u002Fa>, should you prefer a single plugin that does more.\u003C\u002Fp>\n\u003Ch3>What Users Say\u003C\u002Fh3>\n\u003Cp>\u003Cem>“This is \u003Cstrong>a great plugin for dev\u003C\u002Fstrong> especially for people who tinker in the code.”\u003C\u002Fem> ~\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fgreat-for-dev\u002F\" rel=\"ugc\">PK Son\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cem>“I have used a couple of other logger plugins and \u003Cstrong>this is by far the best one\u003C\u002Fstrong>.”\u003C\u002Fem> ~\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fmust-have-plugin-485\u002F\" rel=\"ugc\">Brian Henry\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cem>“\u003Cstrong>Another massive time-saving tool.\u003C\u002Fstrong>“\u003C\u002Fem> ~\u003Ca href=\"https:\u002F\u002Fdigwp.com\u002F2023\u002F06\u002Fplugins-troubleshoot-debug-wordpress\u002F\" rel=\"nofollow ugc\">Jeff Starr\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Give Back\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Freview-dlm\" rel=\"nofollow ugc\">A nice review\u003C\u002Fa> would be great!\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Ffeedback-dlm\" rel=\"nofollow ugc\">Give feedback\u003C\u002Fa> and help improve future versions.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fdebug-log-manager\u002F\" rel=\"nofollow ugc\">Help translate\u003C\u002Fa> into your language.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fgithub-dlm\" rel=\"nofollow ugc\">Github repo\u003C\u002Fa> to contribute code.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbowo.io\u002Fdotorg-sponsor-dlm\" rel=\"nofollow ugc\">Sponsor\u003C\u002Fa> my work.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Check These Out Too\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsystem-dashboard\u002F\" rel=\"ugc\">System Dashboard\u003C\u002Fa>: Central dashboard to monitor various WordPress components, processes and data, including the server.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fvariable-inspector\u002F\" rel=\"ugc\">Variable Inspector\u003C\u002Fa>: Inspect PHP variables on a central dashboard in wp-admin for convenient debugging.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fadmin-site-enhancements\u002F\" rel=\"ugc\">Admin and Site Enhancements\u003C\u002Fa> helps you to easily enhance various admin workflows and site aspects while replacing multiple plugins doing it.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.wpnewsboard.com\u002F\" rel=\"nofollow ugc\">WordPress Newsboard\u003C\u002Fa>: The latest news, articles, podcasts and videos from 100+ WordPress-focused sources.\u003C\u002Fli>\n\u003C\u002Ful>\n","Log PHP, database and JavaScript errors via WP_DEBUG with one click. Conveniently create, view, filter and clear the debug.log file.",10000,116535,24,"2025-09-24T02:30:00.000Z","4.6","5.6",[20,21,101],"errors","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdebug-log-manager\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-log-manager.2.4.3.zip",91,7,"2025-04-18 00:00:00",{"slug":108,"name":109,"version":110,"author":111,"author_profile":112,"description":113,"short_description":114,"active_installs":115,"downloaded":116,"rating":117,"num_ratings":118,"last_updated":119,"tested_up_to":61,"requires_at_least":120,"requires_php":121,"tags":122,"homepage":126,"download_link":127,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":36,"fetched_at":29},"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.1","5.3",[123,124,20,125,23],"administration","conflicts","support","https:\u002F\u002Fnsquared.io","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fplugin-detective.1.2.29.zip",{"slug":129,"name":130,"version":131,"author":132,"author_profile":133,"description":134,"short_description":135,"active_installs":136,"downloaded":137,"rating":13,"num_ratings":138,"last_updated":139,"tested_up_to":16,"requires_at_least":99,"requires_php":99,"tags":140,"homepage":144,"download_link":145,"security_score":146,"vuln_count":14,"unpatched_count":27,"last_vuln_date":147,"fetched_at":29},"debug-log-config-tool","Debug Log – Manager Tool","2.0.1","Lukman Nakib","https:\u002F\u002Fprofiles.wordpress.org\u002Fpyrobd\u002F","\u003Cp>A comprehensive debugging toolkit for WordPress developers and site administrators. This plugin gives you complete control over WordPress debugging without editing wp-config.php files or using FTP.\u003C\u002Fp>\n\u003Ch4>Quick Demo\u003C\u002Fh4>\n\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FD4K5zsLnILw?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>WP-CLI Style Terminal\u003C\u002Fstrong>: Execute WordPress commands directly from your browser with syntax highlighting and auto-completion\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Database Tools\u003C\u002Fstrong>: Run SQL queries, view table structures, and optimize your database (super admin only)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debug Constants Manager\u003C\u002Fstrong>: Toggle all WordPress debug constants with a single click\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Log Viewer\u003C\u002Fstrong>: View, filter, and analyze debug logs with syntax highlighting and error categorization\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Query Inspector\u003C\u002Fstrong>: Examine database queries with SAVEQUERIES support\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Email Notifications\u003C\u002Fstrong>: Get alerts when new errors appear in your logs\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Safe Mode\u003C\u002Fstrong>: Quickly disable all plugins except selected ones for troubleshooting\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom Log Paths\u003C\u002Fstrong>: Set custom log file locations with filter support\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Debug Constants Available\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>WP_DEBUG\u003C\u002Fstrong> – Default Value: true – Enables WordPress debug mode\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DEBUG_LOG\u003C\u002Fstrong> – Default Value: true – Saves all errors to a debug.log file\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SCRIPT_DEBUG\u003C\u002Fstrong> – Default Value: false – Uses development versions of core JS and CSS files\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP_DEBUG_DISPLAY\u003C\u002Fstrong> – Default Value: false – Controls whether debug messages display on screen\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SAVEQUERIES\u003C\u002Fstrong> – Default Value: false – Saves database queries for analysis\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Developer Tools\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Terminal Commands\u003C\u002Fstrong>: Use WP-CLI style commands like \u003Ccode>wp core version\u003C\u002Fcode> or \u003Ccode>wp plugin list\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Database Explorer\u003C\u002Fstrong>: Run SELECT queries and view results in a formatted table\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Stack Trace Analysis\u003C\u002Fstrong>: Visualize error stack traces for easier debugging\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Hook Inspector\u003C\u002Fstrong>: View all registered hooks and their callbacks\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Environment Detection\u003C\u002Fstrong>: Development features are automatically hidden in production\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>Developer API\u003C\u002Fstrong>: Apply custom filters like \u003Ccode>apply_filters('wp_debuglog_log_file_path', $file);\u003C\u002Fcode> to extend functionality\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>Please note: Constant values will be restored on plugin deactivation as it was before activating the plugin.\u003C\u002Fp>\n","The \"Debug Log Config Tool\" simplifies debugging. Toggle logging,queries , view levels, clear logs from dashboard.",3000,56110,21,"2025-04-30T19:04:00.000Z",[20,21,141,142,143],"log","remote-debug","tools","https:\u002F\u002Fnkb-bd.github.io\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-log-config-tool.2.0.1.zip",99,"2024-05-20 00:00:00",{"attackSurface":149,"codeSignals":234,"taintFlows":325,"riskAssessment":326,"analyzedAt":332},{"hooks":150,"ajaxHandlers":207,"restRoutes":230,"shortcodes":231,"cronEvents":232,"entryPointCount":233,"unprotectedCount":27},[151,157,161,165,168,171,174,179,184,188,192,195,200,204],{"type":152,"name":153,"callback":154,"file":155,"line":156},"action","admin_menu","add_admin_menu","debug-troubleshooter.php",66,{"type":152,"name":158,"callback":159,"file":155,"line":160},"admin_enqueue_scripts","enqueue_admin_scripts",67,{"type":152,"name":162,"callback":163,"priority":27,"file":155,"line":164},"plugins_loaded","init_troubleshooting_mode",75,{"type":152,"name":162,"callback":166,"priority":27,"file":155,"line":167},"init_live_debug_mode",76,{"type":152,"name":162,"callback":169,"priority":27,"file":155,"line":170},"init_user_simulation",77,{"type":152,"name":172,"callback":173,"file":155,"line":117},"admin_notices","troubleshooting_mode_notice",{"type":152,"name":175,"callback":176,"priority":177,"file":155,"line":178},"admin_bar_menu","admin_bar_exit_simulation",999,81,{"type":180,"name":181,"callback":182,"file":155,"line":183},"filter","option_active_plugins","filter_active_plugins",489,{"type":180,"name":185,"callback":186,"file":155,"line":187},"site_option_active_sitewide_plugins","filter_active_sitewide_plugins",491,{"type":180,"name":189,"callback":190,"file":155,"line":191},"pre_option_template","filter_theme",495,{"type":180,"name":193,"callback":190,"file":155,"line":194},"pre_option_stylesheet",496,{"type":180,"name":196,"callback":197,"priority":198,"file":155,"line":199},"determine_current_user","simulate_user_filter",20,804,{"type":152,"name":201,"callback":202,"file":155,"line":203},"wp_footer","print_exit_simulation_script",883,{"type":152,"name":205,"callback":202,"file":155,"line":206},"admin_footer",884,[208,214,218,222,226],{"action":209,"nopriv":210,"callback":211,"hasNonce":212,"hasCapCheck":212,"file":155,"line":213},"debug_troubleshoot_toggle_mode",false,"ajax_toggle_troubleshoot_mode",true,68,{"action":215,"nopriv":210,"callback":216,"hasNonce":212,"hasCapCheck":212,"file":155,"line":217},"debug_troubleshoot_update_state","ajax_update_troubleshoot_state",69,{"action":219,"nopriv":210,"callback":220,"hasNonce":212,"hasCapCheck":212,"file":155,"line":221},"debug_troubleshoot_toggle_debug_mode","ajax_toggle_debug_mode",70,{"action":223,"nopriv":210,"callback":224,"hasNonce":212,"hasCapCheck":212,"file":155,"line":225},"debug_troubleshoot_clear_debug_log","ajax_clear_debug_log",71,{"action":227,"nopriv":210,"callback":228,"hasNonce":212,"hasCapCheck":212,"file":155,"line":229},"debug_troubleshoot_toggle_simulate_user","ajax_toggle_simulate_user",72,[],[],[],5,{"dangerousFunctions":235,"sqlUsage":236,"outputEscaping":238,"fileOperations":27,"externalRequests":27,"nonceChecks":233,"capabilityChecks":233,"bundledLibraries":324},[],{"prepared":14,"raw":27,"locations":237},[],{"escaped":239,"rawEcho":240,"locations":241},62,41,[242,245,247,249,251,253,255,257,259,261,263,264,266,268,270,272,274,276,278,280,282,284,286,288,290,292,294,296,298,300,302,304,306,308,310,312,314,316,318,320,322],{"file":155,"line":243,"context":244},190,"raw output",{"file":155,"line":246,"context":244},229,{"file":155,"line":248,"context":244},322,{"file":155,"line":250,"context":244},324,{"file":155,"line":252,"context":244},325,{"file":155,"line":254,"context":244},326,{"file":155,"line":256,"context":244},327,{"file":155,"line":258,"context":244},334,{"file":155,"line":260,"context":244},335,{"file":155,"line":262,"context":244},337,{"file":155,"line":78,"context":244},{"file":155,"line":265,"context":244},356,{"file":155,"line":267,"context":244},358,{"file":155,"line":269,"context":244},360,{"file":155,"line":271,"context":244},380,{"file":155,"line":273,"context":244},382,{"file":155,"line":275,"context":244},383,{"file":155,"line":277,"context":244},384,{"file":155,"line":279,"context":244},385,{"file":155,"line":281,"context":244},386,{"file":155,"line":283,"context":244},387,{"file":155,"line":285,"context":244},388,{"file":155,"line":287,"context":244},389,{"file":155,"line":289,"context":244},390,{"file":155,"line":291,"context":244},391,{"file":155,"line":293,"context":244},396,{"file":155,"line":295,"context":244},398,{"file":155,"line":297,"context":244},401,{"file":155,"line":299,"context":244},403,{"file":155,"line":301,"context":244},404,{"file":155,"line":303,"context":244},405,{"file":155,"line":305,"context":244},406,{"file":155,"line":307,"context":244},411,{"file":155,"line":309,"context":244},413,{"file":155,"line":311,"context":244},414,{"file":155,"line":313,"context":244},415,{"file":155,"line":315,"context":244},416,{"file":155,"line":317,"context":244},417,{"file":155,"line":319,"context":244},422,{"file":155,"line":321,"context":244},456,{"file":155,"line":323,"context":244},459,[],[],{"summary":327,"deductions":328},"The 'debugger-troubleshooter' plugin v1.3.2 exhibits a generally good security posture based on the static analysis.  All identified entry points, including the 5 AJAX handlers, have proper nonce and capability checks.  The plugin also avoids dangerous functions, file operations, and external HTTP requests, and all SQL queries are properly prepared. This indicates a strong adherence to secure coding practices.\n\nHowever, there is a notable concern regarding output escaping, with only 60% of outputs being properly escaped. This leaves a significant portion of the output susceptible to cross-site scripting (XSS) vulnerabilities if user-supplied data is involved in these unescaped outputs. The absence of any taint analysis results is also a slight unknown, as it means potential vulnerabilities in data flow were not detected by that specific method. The plugin's history of zero vulnerabilities is a positive sign, suggesting consistent secure development or a lack of focus from attackers, but it does not negate the potential risks identified in the current code analysis.\n\nIn conclusion, while the plugin demonstrates strengths in authentication, authorization, and SQL handling, the significant percentage of unescaped output presents a clear and present risk. Addressing the output escaping issues should be the primary focus to improve its overall security. The lack of past vulnerabilities is encouraging but should be viewed in conjunction with the current findings.",[329],{"reason":330,"points":331},"Unescaped output identified",8,"2026-03-16T22:05:26.538Z",{"wat":334,"direct":343},{"assetPaths":335,"generatorPatterns":338,"scriptPaths":339,"versionParams":340},[336,337],"\u002Fwp-content\u002Fplugins\u002Fdebugger-troubleshooter\u002Fassets\u002Fcss\u002Fadmin.css","\u002Fwp-content\u002Fplugins\u002Fdebugger-troubleshooter\u002Fassets\u002Fjs\u002Fadmin.js",[],[337],[341,342],"debugger-troubleshooter\u002Fassets\u002Fcss\u002Fadmin.css?ver=","debugger-troubleshooter\u002Fassets\u002Fjs\u002Fadmin.js?ver=",{"cssClasses":344,"htmlComments":353,"htmlAttributes":354,"restEndpoints":360,"jsGlobals":362,"shortcodeOutput":364},[345,346,347,348,349,350,351,352],"debug-troubleshooter-wrap","debug-troubleshooter-content","debug-troubleshooter-section","section-header","section-content","standalone-section","troubleshoot-mode-controls","debug-troubleshooter-card",[],[355,356,357,358,359],"id=\"copy-site-info\"","id=\"troubleshoot-mode-toggle\"","id=\"troubleshoot-theme-select\"","data-nonce","data-ajax-url",[361],"\u002Fwp-json\u002Fdebugger-troubleshooter\u002Fv1\u002Fadmin-ajax.php",[363],"debugTroubleshoot",[]]