[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fXugshZj6YH02qFFfgecN-nzMtKYfWh_mtAPzRnSAkKo":3,"$f9MaYMpo9Li5YY6xeZHAEE7IfIbE0mHRgPZ6g4kBjHD8":220,"$fZ20fOYWnZh3sc8lEMwV1Bc_3O9Avo8vhlSeSroEwn8c":225},{"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":27,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"discovery_status":31,"vulnerabilities":32,"developer":51,"crawl_stats":38,"alternatives":55,"analysis":164,"fingerprints":203},"debug","Debug","1.12","SoniNow","https:\u002F\u002Fprofiles.wordpress.org\u002Fsoninow\u002F","\u003Cp>Debug can help you to find errors in your wordpress website via editing wp-config.php file. you may enable error reporting by debug plugin. enable email notification on any run time bug in wordpress CMS\u002Fwebsite.\u003C\u002Fp>\n\u003Ch3>A brief Debug\u003C\u002Fh3>\n\u003Cp>Ordered list:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Debug in wordpress rewrite wp-config.php file via error_log function in php.\u003C\u002Fli>\n\u003Cli>if you don’t have file write permission. so don’t use this plugin.\u003C\u002Fli>\n\u003Cli>keep backup your wp-config file before save plugin setting.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>How to contact the support \u002F development team of our Debug plugin\u003C\u002Fh4>\n\u003Cp>You can contact us through,\u003Cbr \u002F>\nhttps:\u002F\u002Fsoninow.com\u002Fcontact\u003C\u002Fp>\n","Debug can help you to find errors in your wordpress website via editing wp-config.php file and email notification.",2000,93772,92,11,"2024-04-01T14:15:00.000Z","6.4.8","3.4","5.6",[4,20,21,22,23],"display-error","error-log","error-notification","error-reporting","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug.1.12.zip",85,1,0,"2024-01-31 00:00:00","2026-04-16T10:56:18.058Z","no_bundle",[33],{"id":34,"url_slug":35,"title":36,"description":37,"plugin_slug":4,"theme_slug":38,"affected_versions":39,"patched_in_version":40,"severity":41,"cvss_score":42,"cvss_vector":43,"vuln_type":44,"published_date":29,"updated_date":45,"references":46,"days_to_patch":48,"patch_diff_files":49,"patch_trac_url":38,"research_status":38,"research_verified":50,"research_rounds_completed":28,"research_plan":38,"research_summary":38,"research_vulnerable_code":38,"research_fix_diff":38,"research_exploit_outline":38,"research_model_used":38,"research_started_at":38,"research_completed_at":38,"research_error":38,"poc_status":38,"poc_video_id":38,"poc_summary":38,"poc_steps":38,"poc_tested_at":38,"poc_wp_version":38,"poc_php_version":38,"poc_playwright_script":38,"poc_exploit_code":38,"poc_has_trace":50,"poc_model_used":38,"poc_verification_depth":38},"CVE-2024-24798","debug-cross-site-request-forgery","Debug \u003C= 1.10 - Cross-Site Request Forgery","The Debug plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.10. This is due to missing nonce validation. This makes it possible for unauthenticated attackers to clear the debug log via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.",null,"\u003C=1.10","1.11","medium",4.3,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:U\u002FC:N\u002FI:L\u002FA:N","Cross-Site Request Forgery (CSRF)","2024-04-01 20:39:59",[47],"https:\u002F\u002Fwww.wordfence.com\u002Fthreat-intel\u002Fvulnerabilities\u002Fid\u002Faa7276bb-6a9b-4cbd-8333-14c4dfac4108?source=api-prod",62,[],false,{"slug":52,"display_name":7,"profile_url":8,"plugin_count":27,"total_installs":11,"avg_security_score":26,"avg_patch_time_days":48,"trust_score":53,"computed_at":54},"soninow",78,"2026-05-20T01:09:03.764Z",[56,80,103,124,144],{"slug":57,"name":58,"version":59,"author":60,"author_profile":61,"description":62,"short_description":63,"active_installs":64,"downloaded":65,"rating":66,"num_ratings":67,"last_updated":68,"tested_up_to":69,"requires_at_least":70,"requires_php":18,"tags":71,"homepage":75,"download_link":76,"security_score":77,"vuln_count":78,"unpatched_count":27,"last_vuln_date":79,"fetched_at":30},"error-log-viewer-wp","Error Log Viewer By WP Guru","1.0.5","WP Guru","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpguruin\u002F","\u003Ch3>Best Error Log Viewer Plugin for WordPress\u003C\u002Fh3>\n\u003Cp>A Lightweight Plugin to Handle Error Logs easily and efficiently.\u003C\u002Fp>\n\u003Cp>Error Log Viewer By WP Guru is a great Free WordPress plugin if you are looking to manage Error log entries and kill errors on time. Error logs help you monitor your site and provide visibility into important changes that occur on your website. PHP error logs, including WordPress logs, can help you to spot problems and identify the offending plugin, theme, or custom code.\u003C\u002Fp>\n\u003Cp>Logging errors is considered one of the top “best practices” in software development; it becomes more important as your website grows and scales.\u003C\u002Fp>\n\u003Cp>Additionally, you can track all types of errors based on Plugins, Themes, and WP Core or custom code and resolve exceptions to get optimized performance results.\u003C\u002Fp>\n\u003Cp>Monitoring PHP errors is something you need to do if you want to keep your WordPress website secure, healthy, and fast. If not fixed, PHP errors can indeed reduce your website performance and increase your website’s vulnerability to downtime and hackers.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Like this plugin?\u003C\u002Fstrong> Consider leaving a \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fview\u002Fplugin-reviews\u002Ferror-log-viewer-wp?filter=5\" rel=\"ugc\">5 star review\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Filter Error Log by Date\u003C\u002Fli>\n\u003Cli>Filter Error Log by Error types\u003C\u002Fli>\n\u003Cli>Error Log statistics based on Plugins and Themes as well\u003C\u002Fli>\n\u003Cli>Download the Log File\u003C\u002Fli>\n\u003Cli>Delete Log File\u003C\u002Fli>\n\u003C\u002Ful>\n","Error Log Viewer by WP Guru simplifies viewing and analyzing PHP error logs, making it easier to monitor and resolve errors quickly.",100,3479,90,8,"2025-01-02T05:25:00.000Z","6.7.5","5.4",[72,73,21,23,74],"admin","debug-tool","log-report","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ferror-log-viewer-wp\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ferror-log-viewer-wp.1.0.5.zip",68,2,"2025-04-09 00:00:00",{"slug":81,"name":82,"version":83,"author":84,"author_profile":85,"description":86,"short_description":87,"active_installs":88,"downloaded":89,"rating":90,"num_ratings":91,"last_updated":92,"tested_up_to":93,"requires_at_least":94,"requires_php":24,"tags":95,"homepage":98,"download_link":99,"security_score":100,"vuln_count":101,"unpatched_count":28,"last_vuln_date":102,"fetched_at":30},"error-log-viewer","Error Log Viewer by BestWebSoft","1.1.8","bestwebsoft","https:\u002F\u002Fprofiles.wordpress.org\u002Fbestwebsoft\u002F","\u003Cp>Simple utility plugin that helps to find and view log files with errors right from your WordPress admin dashboard. Get access to all your log files from one place. View the latest activity, select logs by date, or view a full log file. Get email notifications about log changes.\u003C\u002Fp>\n\u003Cp>Get access to your website logs and troubleshoot issues faster!\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fdemo-error-log-viewer\u002F?ref=readme\" rel=\"nofollow ugc\">View Demo\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\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\u002F8LR0F4GgXhM?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>\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Enable WordPress error logging with:\n\u003Cul>\n\u003Cli>.htaccess\u003C\u002Fli>\n\u003Cli>wp-config.php using \u003Ccode>inl_set\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>wp-config.php using \u003Ccode>WP_DEBUG\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Search and view error logs:\n\u003Cul>\n\u003Cli>PHP\u003C\u002Fli>\n\u003Cli>WordPress\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Configure email notifications about log changes:\n\u003Cul>\n\u003Cli>Set the email\u003C\u002Fli>\n\u003Cli>Change frequency\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Configure log monitor settings:\n\u003Cul>\n\u003Cli>Choose the log to be displayed\u003C\u002Fli>\n\u003Cli>Choose what to show in the log:\n\u003Cul>\n\u003Cli>Certain last lines in the file\u003C\u002Fli>\n\u003Cli>Log for a certain period of time\u003C\u002Fli>\n\u003Cli>Full file\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>View or save the part of PHP error logs as TXT file\u003C\u002Fli>\n\u003Cli>Compatible with latest WordPress version\u003C\u002Fli>\n\u003Cli>Incredibly simple settings for fast setup without modifying code\u003C\u002Fli>\n\u003Cli>Detailed step-by-step documentation and videos\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you have a feature suggestion or idea you’d like to see in the plugin, we’d love to hear about it! \u003Ca href=\"https:\u002F\u002Fsupport.bestwebsoft.com\u002Fhc\u002Fen-us\u002Frequests\u002Fnew\" rel=\"nofollow ugc\">Suggest a Feature\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Documentation & Videos\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fdocumentation\u002Ferror-log-viewer\u002Ferror-log-viewer-user-guide\u002F\" rel=\"nofollow ugc\">[Doc] User Guide\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fdocumentation\u002Fhow-to-install-a-wordpress-product\u002Fhow-to-install-a-wordpress-plugin\u002F\" rel=\"nofollow ugc\">[Doc] Installation\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Help & Support\u003C\u002Fh4>\n\u003Cp>Visit our Help Center if you have any questions, our friendly Support Team is happy to help – \u003Ca href=\"https:\u002F\u002Fsupport.bestwebsoft.com\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fsupport.bestwebsoft.com\u002F\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Affiliate Program\u003C\u002Fh4>\n\u003Cp>Earn 20% commission by selling the premium WordPress plugins and themes by BestWebSoft — https:\u002F\u002Fbestwebsoft.com\u002Faffiliate\u002F\u003C\u002Fp>\n\u003Ch4>Translation\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Russian (ru_RU)\u003C\u002Fli>\n\u003Cli>Ukrainian (uk)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Some of these translations are not complete. We are constantly adding new features which should be translated. If you would like to create your own language pack or update the existing one, you can send \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FTranslating_WordPress\" rel=\"nofollow ugc\">the text of PO and MO files\u003C\u002Fa> to \u003Ca href=\"https:\u002F\u002Fsupport.bestwebsoft.com\u002Fhc\u002Fen-us\u002Frequests\u002Fnew\" rel=\"nofollow ugc\">BestWebSoft\u003C\u002Fa> and we’ll add it to the plugin. You can download the latest version of the program for work with PO and MO \u003Ca href=\"https:\u002F\u002Fwww.poedit.net\u002Fdownload.php\" rel=\"nofollow ugc\">files Poedit\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Recommended Plugins\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fproducts\u002Fwordpress\u002Fplugins\u002Fupdater\u002F?k=e2d89a7eca0a903ab58d99e7ffa3b510\" rel=\"nofollow ugc\">Updater\u003C\u002Fa> – Automatically check and update WordPress website core with all installed plugins and themes to the latest versions.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Credits\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>This plugin incorporates a license verification mechanism to ensure the authenticity of your license key and provide access to premium features and updates. The verification process involves connecting securely to our external service hosted at BestWebSoft website \u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\" rel=\"nofollow ugc\">https:\u002F\u002Fbestwebsoft.com\u003C\u002Fa>. Privacy Policy \u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fprivacy-policy\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fbestwebsoft.com\u002Fprivacy-policy\u002F\u003C\u002Fa>. End user license agreement \u003Ca href=\"https:\u002F\u002Fbestwebsoft.com\u002Fend-user-license-agreement\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fbestwebsoft.com\u002Fend-user-license-agreement\u002F\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n","Get latest error log messages to diagnose website problems. Define and fix issues faster.",6000,95464,96,9,"2025-12-03T11:15:00.000Z","6.9.4","6.2",[96,73,21,81,97],"add-debug-tool","php-error-log","https:\u002F\u002Fbestwebsoft.com\u002Fproducts\u002Fwordpress\u002Fplugins\u002Ferror-log-viewer\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ferror-log-viewer.1.1.8.zip",94,5,"2025-10-10 20:39:18",{"slug":104,"name":105,"version":106,"author":107,"author_profile":108,"description":109,"short_description":110,"active_installs":111,"downloaded":112,"rating":113,"num_ratings":114,"last_updated":115,"tested_up_to":93,"requires_at_least":116,"requires_php":117,"tags":118,"homepage":24,"download_link":121,"security_score":122,"vuln_count":27,"unpatched_count":28,"last_vuln_date":123,"fetched_at":30},"debug-log-viewer","Debug Log Viewer","2.1","Oleksandr Lysyi","https:\u002F\u002Fprofiles.wordpress.org\u002Flysyiweb\u002F","\u003Cp>Debug Log Viewer: Your Essential WordPress Debugging Tool\u003C\u002Fp>\n\u003Cp>Tired of struggling to access and understand your WordPress debug.log file?  Debug Log Viewer simplifies WordPress debugging by providing a user-friendly interface to view, search, and manage your debug.log directly within your WordPress admin area.  It’s the perfect solution for WordPress developers, site administrators, and anyone needing to quickly identify and resolve website issues.\u003C\u002Fp>\n\u003Cp>Gain Real-Time Insights into Your WordPress Site Health\u003C\u002Fp>\n\u003Cp>This plugin is designed to provide you with instant visibility into the inner workings of your WordPress website. By tracking errors, warnings, and deprecated function notices in real-time, Debug Log Viewer empowers you to proactively maintain a healthy and stable WordPress environment.\u003C\u002Fp>\n\u003Cp>Key Features for Efficient WordPress Debugging:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Real-Time Log Viewer:  Monitor your WordPress debug.log file in real-time, directly from your WordPress dashboard. No more hunting for files via FTP or cPanel!\u003C\u002Fli>\n\u003Cli>Easy Debug Log Access:  Access and view your full WordPress debug log within a clean and intuitive interface.\u003C\u002Fli>\n\u003Cli>Search and Filtering: Quickly find specific log entries with powerful search and filtering options. Filter by error type, keywords, or date (future feature) to pinpoint issues fast.\u003C\u002Fli>\n\u003Cli>Pagination: Navigate through large debug logs with ease using pagination, ensuring smooth performance even with extensive logs.\u003C\u002Fli>\n\u003Cli>Email Alerts for Critical Errors:  Get immediate email alerts when new errors are logged, allowing you to address critical issues before they impact your users (future feature: configurable severity levels).\u003C\u002Fli>\n\u003Cli>Flexible Settings Panel:\n\u003Cul>\n\u003Cli>Control WP_DEBUG Constants:  Enable or disable WP_DEBUG and WP_DEBUG_LOG constants directly from the plugin settings, without editing wp-config.php.\u003C\u002Fli>\n\u003Cli>Customize Logging Options: Configure your debug log settings to match your specific needs.\u003C\u002Fli>\n\u003Cli>Tailor Your Error Tracking:  Personalize your debugging experience through plugin settings.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Custom Log Path Support:  If you’ve defined a custom path for your debug.log file (e.g., using define( ‘WP_DEBUG_LOG’, ABSPATH . ‘wp-content\u002Flogs\u002Fdebug.log’ );), Debug Log Viewer automatically detects and reads from it.\u003C\u002Fli>\n\u003Cli>Automatic Log Cleanup:  Schedule automatic cleanup to prevent your debug.log from growing too large and consuming disk space. Keep your site running smoothly with automatic maintenance at 50MB threshold.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Benefits of Using Debug Log Viewer:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Save Time and  Effort: Stop wasting time manually accessing and parsing your debug log file. Debug Log Viewer puts all the information you need at your fingertips within WordPress admin.\u003C\u002Fli>\n\u003Cli>Faster Error Detection: Real-time monitoring and email alerts help you catch errors as they happen, minimizing potential downtime.\u003C\u002Fli>\n\u003Cli>Simplified WordPress Troubleshooting:  Quickly identify the source of errors and warnings to streamline your WordPress troubleshooting process.\u003C\u002Fli>\n\u003Cli>Improved Website Stability: Proactive error monitoring and resolution contribute to a more stable and reliable WordPress website.\u003C\u002Fli>\n\u003Cli>User-Friendly Interface:  No coding skills required!  Debug Log Viewer is designed for ease of use, making debug log management accessible to everyone.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Debug Log Viewer Pro Features:\u003C\u002Fp>\n\u003Cp>Upgrade to Pro for advanced debugging capabilities:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Advanced Email Alert Customization: Choose specific error levels to monitor and reduce notification noise.\u003C\u002Fli>\n\u003Cli>CSV Export: Export debug log data for analysis, reporting, or sharing with team members.\u003C\u002Fli>\n\u003Cli>Custom Date Range Filtering: Filter log entries by specific time periods for targeted troubleshooting.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Who is Debug Log Viewer For?\u003C\u002Fp>\n\u003Cul>\n\u003Cli>WordPress developers\u003C\u002Fli>\n\u003Cli>Website administrators\u003C\u002Fli>\n\u003Cli>Freelancers managing client sites\u003C\u002Fli>\n\u003Cli>Anyone who wants an easy way to monitor WordPress errors and improve website health\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Tested up to\u003C\u002Fh3>\n\u003Cp>WordPress Version: 6.9\u003Cbr \u002F>\nPHP Version: 8.3.9\u003C\u002Fp>\n","Effortlessly view, search, filter and manage your WordPress debug.log in the admin dashboard. Real-time monitoring and email alerts",1000,12513,80,3,"2026-03-02T06:29:00.000Z","5.8","7.2",[4,119,21,120],"debugging","log","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-log-viewer.2.1.zip",99,"2025-10-29 00:00:00",{"slug":125,"name":126,"version":127,"author":128,"author_profile":129,"description":130,"short_description":131,"active_installs":132,"downloaded":133,"rating":64,"num_ratings":27,"last_updated":134,"tested_up_to":135,"requires_at_least":136,"requires_php":24,"tags":137,"homepage":24,"download_link":141,"security_score":122,"vuln_count":27,"unpatched_count":28,"last_vuln_date":142,"fetched_at":143},"code-quality-control-tool","Code Quality Control Tool","2.2","nickclarkweb","https:\u002F\u002Fprofiles.wordpress.org\u002Fnickclarkweb\u002F","\u003Cp>A PHP plugin or theme might produce many different levels of earning and errors during its execution. Being able to see these errors is essential for website owners trying to troubleshoot a misbehaving module or theme. If you are having problems with your WordPress CMS or plugins and need to log and display all the errors and warnings, our plugin is the best solution for you.\u003C\u002Fp>\n\u003Cp>During production, error messages must not be shown to the end users, but this information must still be recorded for tracing purposes. The best way to record these error messages on a production web application is to store it in log files. This is exactly what our plugin does. It stores all PHP errors to log file so you would be able to see what caused the problem.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Here are some main features:\u003C\u002Fstrong>\u003Cbr \u002F>\n* You can log all errors for separate plugins and themes. No need to log all the eroors, just get the plugins you care about under control.\u003Cbr \u002F>\n* Shows date, detected file and URL with the issue, line of code with the issue and type of error and issue description.\u003Cbr \u002F>\n* Log and monitor PHP errors just for your IP address. So noone else could see the errors.\u003Cbr \u002F>\n* Filtering by PHP error type\u003Cbr \u002F>\n* Filtering by file or folder or plugin folder or theme folder\u003Cbr \u002F>\n* Log unique errors to minimize analyze time.\u003Cbr \u002F>\n* See the last errors in WordPress admin section\u003Cbr \u002F>\n* Log file download\u003Cbr \u002F>\n* Deep debug more will not slow down the website\u003C\u002Fp>\n\u003Cp>Trace all PHP error types:\u003Cbr \u002F>\nE_ERROR, E_WARNING, E_PARSE, E_NOTICE, E_CORE_ERROR, E_CORE_WARNING, E_COMPILE_ERROR, E_COMPILE_WARNING, E_USER_ERROR, E_USER_WARNING, E_USER_NOTICE, E_STRICT, E_RECOVERABLE_ERROR, E_DEPRECATED, E_USER_DEPRECATED\u003C\u002Fp>\n","Plugin that allows you to see all PHP errors and helps you troubleshoot a misbehaving theme or plugin.",60,2471,"2025-10-28T11:00:00.000Z","6.8.5","3.0",[138,4,139,21,140],"code-analyzer","error-handling","tools","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcode-quality-control-tool.2.2.zip","2025-10-10 20:31:38","2026-04-06T09:54:40.288Z",{"slug":145,"name":146,"version":147,"author":148,"author_profile":149,"description":150,"short_description":151,"active_installs":152,"downloaded":153,"rating":64,"num_ratings":78,"last_updated":154,"tested_up_to":93,"requires_at_least":155,"requires_php":156,"tags":157,"homepage":161,"download_link":162,"security_score":122,"vuln_count":27,"unpatched_count":28,"last_vuln_date":163,"fetched_at":30},"0-day-analytics","0 Day Analytics","5.0.0","Golemiq","https:\u002F\u002Fprofiles.wordpress.org\u002Fawesomefootnotes\u002F","\u003Cp>\u003Cstrong>0 Day Analytics\u003C\u002Fstrong> is a comprehensive WordPress debugging and operational\u003Cbr \u002F>\nintelligence plugin. It is purpose-built for developers and site administrators\u003Cbr \u002F>\nwho need real-time visibility into their PHP errors, scheduled tasks, database\u003Cbr \u002F>\nstate, outgoing emails, HTTP requests, hook behaviour, and overall site health —\u003Cbr \u002F>\nall from a single admin interface.\u003C\u002Fp>\n\u003Cp>Unlike general monitoring services, 0 Day Analytics runs entirely inside your\u003Cbr \u002F>\nWordPress installation with no third-party data collection. Every module is\u003Cbr \u002F>\nopt-in and designed with performance in mind.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Plugin Website:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002F0-day-analytics.com\u002F0-day-analytics-wordpress-debugging-monitoring-toolkit\u002F?src=readme\" rel=\"nofollow ugc\">0-day-analytics.com\u003C\u002Fa>\u003Cbr \u002F>\n\u003Cstrong>User Documentation:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002F0-day-analytics.com\u002Fcategory\u002F0-day-plugin\u002Fuser-guide\u002F?src=readme\" rel=\"nofollow ugc\">User Guide\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Error Log Manager\u003C\u002Fh4>\n\u003Cp>Read, search, filter, and manage your PHP\u002FWordPress error log without leaving\u003Cbr \u002F>\nthe admin. Engineered for very large (GB-sized) logs using a reverse-line reader\u003Cbr \u002F>\nthat never performs a full-file read. Supports code-context viewing (click any\u003Cbr \u002F>\nerror to see the surrounding source), per-severity filtering, log truncation,\u003Cbr \u002F>\nand download. Optionally randomise the log filename to reduce exposure.\u003C\u002Fp>\n\u003Ch4>PHP Fatal Error Tracker\u003C\u002Fh4>\n\u003Cp>Captures and stores PHP fatal errors in a dedicated database table, it records PHP errors even if the WP_DEBUG is turned off so they persist even after the log is rotated or overwritten. Each record includes\u003Cbr \u002F>\nerror type, file, line, stack trace, and timestamp — searchable and filterable\u003Cbr \u002F>\ndirectly in the admin.\u003C\u002Fp>\n\u003Ch4>Site Performance & Security Scanner\u003C\u002Fh4>\n\u003Cp>Runs 32+ automated checks across three categories — Security, Speed, and\u003Cbr \u002F>\nResources used — and presents a scored dashboard with actionable\u003Cbr \u002F>\nrecommendations. Checks include: PHP version, WordPress version, SSL\u003Cbr \u002F>\ncertificate, debug mode exposure, file permissions, database prefix, XML-RPC,\u003Cbr \u002F>\nlogin URL, active plugin count, autoloaded options, cron health, page caching,\u003Cbr \u002F>\nobject caching, gzip compression, lazy loading, image optimisation, and more.\u003C\u002Fp>\n\u003Ch4>Google PageSpeed & Core Web Vitals\u003C\u002Fh4>\n\u003Cp>Analyse any URL directly from the WordPress admin using the Google PageSpeed\u003Cbr \u002F>\nInsights API. Displays Performance, Accessibility, Best Practices, and SEO\u003Cbr \u002F>\nscores with Lighthouse category breakdowns for both desktop and mobile. For that you need to provide your own PageSpeed Google API key.\u003C\u002Fp>\n\u003Ch4>URL Tracker & Asset Analyser\u003C\u002Fh4>\n\u003Cp>Automatically tracks visited page URLs on your site. For each recorded URL,\u003Cbr \u002F>\nyou can collect all associated JS, CSS, and media assets (with file sizes), run\u003Cbr \u002F>\na Google PageSpeed analysis, and review visit counts — making it easy to audit\u003Cbr \u002F>\npage weight and performance regressions over time.\u003C\u002Fp>\n\u003Ch4>Cron Manager\u003C\u002Fh4>\n\u003Cp>View, search, edit, manually run, and delete WordPress scheduled tasks. Shows\u003Cbr \u002F>\nnext run time (UTC), recurrence interval, arguments, and last execution status.\u003Cbr \u002F>\nSupports bulk actions and advanced filtering.\u003C\u002Fp>\n\u003Ch4>Transients Manager\u003C\u002Fh4>\n\u003Cp>Browse, search, edit, and safely delete database transients. Displays expiry\u003Cbr \u002F>\ntime, serialised value (pretty-printed), and size. Bulk delete supports\u003Cbr \u002F>\nfiltered selections.\u003C\u002Fp>\n\u003Ch4>Outgoing HTTP Requests Viewer\u003C\u002Fh4>\n\u003Cp>Logs all outgoing \u003Ccode>wp_remote_*\u003C\u002Fcode> calls made by WordPress core, themes, and\u003Cbr \u002F>\nplugins. Records URL, method, status code, response time, triggering plugin,\u003Cbr \u002F>\nuser, and full request\u002Fresponse detail. Export to CSV for external analysis.\u003Cbr \u002F>\nAdvanced filtering by domain, plugin, status, and date range.\u003C\u002Fp>\n\u003Ch4>Mail Logger & Composer\u003C\u002Fh4>\n\u003Cp>Records every email sent through \u003Ccode>wp_mail()\u003C\u002Fcode> — including headers, body,\u003Cbr \u002F>\nattachments, CC, and BCC — and stores it in a searchable log. View the\u003Cbr \u002F>\nrendered email body, resend any logged email, or compose and send new emails\u003Cbr \u002F>\ndirectly from the admin. Supports HTML and plain-text previews.\u003C\u002Fp>\n\u003Ch4>SMTP Configuration\u003C\u002Fh4>\n\u003Cp>Configure custom SMTP settings (host, port, encryption, username, password)\u003Cbr \u002F>\nwith a built-in test email tool. Optionally log SMTP debug output to the\u003Cbr \u002F>\nWordPress debug log.\u003C\u002Fp>\n\u003Ch4>WP Hooks Monitor\u003C\u002Fh4>\n\u003Cp>Define which WordPress actions and filters (core or custom) you want to\u003Cbr \u002F>\nobserve. The Hooks Capture module records each invocation with its parameters,\u003Cbr \u002F>\nreturn value (for filters), and a full stack backtrace. Organise monitoring\u003Cbr \u002F>\nrules into named groups, enable\u002Fdisable per hook, and review the captured\u003Cbr \u002F>\noutput in a dedicated list view.\u003C\u002Fp>\n\u003Ch4>DB Table Manager\u003C\u002Fh4>\n\u003Cp>Browse, search, edit, and delete records across any table in your\u003Cbr \u002F>\nWordPress database — including custom plugin tables. Displays table size,\u003Cbr \u002F>\nengine, collation, row count, and schema information. Supports full and\u003Cbr \u002F>\nfiltered truncation and table drop with confirmation.\u003C\u002Fp>\n\u003Ch4>Server Info & System Status\u003C\u002Fh4>\n\u003Cp>Displays real-time server metrics (CPU load, memory usage, disk space,\u003Cbr \u002F>\nPHP version, active extensions) as both admin-bar badges and a dashboard\u003Cbr \u002F>\nwidget. Also provides a detailed environment report useful for support tickets\u003Cbr \u002F>\nand deployment checks.\u003C\u002Fp>\n\u003Ch4>Plugin Version Switcher\u003C\u002Fh4>\n\u003Cp>Roll back or switch between any previously downloaded version of an installed\u003Cbr \u002F>\nplugin without leaving the admin. Useful for quickly reverting after a bad\u003Cbr \u002F>\nupdate. Supports only free plugins from the WordPress repo.\u003C\u002Fp>\n\u003Ch4>Code Snippets\u003C\u002Fh4>\n\u003Cp>Write, save, and execute custom PHP snippets from the admin. Snippets support\u003Cbr \u002F>\nshortcodes, can be enabled\u002Fdisabled individually, and are sandboxed before\u003Cbr \u002F>\nexecution. Useful for one-off data migrations, testing custom logic, or\u003Cbr \u002F>\ngenerating dynamic output without creating a custom plugin.\u003C\u002Fp>\n\u003Ch4>REST API Manager\u003C\u002Fh4>\n\u003Cp>A security and management tool that gives full visibility and control over\u003Cbr \u002F>\nevery registered REST API endpoint (\u003Ccode>\u002Fwp-json\u002F\u003C\u002Fcode>). Inspect all registered\u003Cbr \u002F>\nroutes, disable individual endpoints, restrict HTTP methods, and hide routes\u003Cbr \u002F>\nfrom discovery responses. Useful for hardening your site by removing\u003Cbr \u002F>\nunnecessary API surface area.\u003C\u002Fp>\n\u003Ch4>WP Panel\u003C\u002Fh4>\n\u003Cp>A centralised control panel for toggling WordPress core features and settings.\u003Cbr \u002F>\nEnable or disable comments, revisions, auto-updates, XML-RPC, the REST API,\u003Cbr \u002F>\nemojis, embeds, heartbeat behaviour, frontend asset loading, and more — all\u003Cbr \u002F>\nfrom a single, organised admin page. No code changes or custom snippets\u003Cbr \u002F>\nrequired.\u003C\u002Fp>\n\u003Ch4>Recovery Mode\u003C\u002Fh4>\n\u003Cp>Generate single-use recovery links that can disable a specific plugin or\u003Cbr \u002F>\ntrigger a custom action — delivered via Slack, Telegram, or any configured\u003Cbr \u002F>\nwebhook channel. Designed for emergency recovery when the site is inaccessible\u003Cbr \u002F>\nthrough normal means. The recovery URLs are sent in Slack and Telegram channels for security.\u003C\u002Fp>\n\u003Ch4>Other Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Dark mode for all admin screens.\u003C\u002Fli>\n\u003Cli>CSV export on all list views (requests, errors, mails, hooks, etc.).\u003C\u002Fli>\n\u003Cli>Screen Options on every screen (configure columns, items per page).\u003C\u002Fli>\n\u003Cli>WP CLI compatible scaffolding for background operations.\u003C\u002Fli>\n\u003Cli>Multisite aware (note: recovery mode has core multisite limitations).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Short Description\u003C\u002Fh3>\n\u003Cp>All-in-one WordPress debug & operations toolkit: error log manager, PHP fatal\u003Cbr \u002F>\ntracker, cron & transient manager, mail logger, SMTP, outgoing requests viewer,\u003Cbr \u002F>\nDB table manager, site performance & security scanner, Google PageSpeed\u003Cbr \u002F>\nintegration, URL tracker, WP hooks monitor, code snippets, and recovery mode.\u003C\u002Fp>\n\u003Ch3>Requirements & Compatibility\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>WordPress 6.0+ (tested up to 6.9)\u003C\u002Fli>\n\u003Cli>PHP 7.4+ (compatible with PHP 8.0, 8.1, 8.2, 8.3, 8.4, 8.5)\u003C\u002Fli>\n\u003Cli>MySQL 5.7+ \u002F MariaDB 10.3+\u003C\u002Fli>\n\u003Cli>Not intended as a primary multisite recovery tool (see FAQ)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Best Practices & Security Notes\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Keep log files outside the webroot when possible, or restrict access via\u003Cbr \u002F>\nserver rules (.htaccess \u002F nginx) to prevent public exposure.\u003C\u002Fli>\n\u003Cli>Use the built-in “Randomise Log Filename” feature when logs must stay in the\u003Cbr \u002F>\nwebroot.\u003C\u002Fli>\n\u003Cli>All plugin capabilities are restricted to \u003Ccode>manage_options\u003C\u002Fcode> (administrators)\u003Cbr \u002F>\nby default. The menu can optionally be restricted to admins only.\u003C\u002Fli>\n\u003Cli>Sanitize and escape all output; nonces are enforced on all state-changing\u003Cbr \u002F>\nactions.\u003C\u002Fli>\n\u003Cli>Secure SMTP credentials using TLS\u002FSTARTTLS; credentials are stored in the\u003Cbr \u002F>\nWordPress options table.\u003C\u002Fli>\n\u003Cli>Set file permissions tightly (e.g., 600\u002F640) and restrict ownership to the\u003Cbr \u002F>\nweb server user.\u003C\u002Fli>\n\u003Cli>Backup database and files before using bulk delete or table truncation.\u003C\u002Fli>\n\u003Cli>Disable unused modules to reduce footprint and potential attack surface.\u003C\u002Fli>\n\u003Cli>Disable or throttle high-frequency background polling on high-load sites.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Usage Notes & Performance\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>The Error Log viewer reads the last N lines (default 100, max configurable\u003Cbr \u002F>\nvia Screen Options) to avoid full-file reads on GB-sized logs.\u003C\u002Fli>\n\u003Cli>No pagination on error logs by design — pagination would force repeated\u003Cbr \u002F>\nexpensive full-file reads.\u003C\u002Fli>\n\u003Cli>The PHP Fatal Error Tracker uses its own DB table; apply a retention policy\u003Cbr \u002F>\nin Settings to avoid unbounded growth.\u003C\u002Fli>\n\u003Cli>The Hooks Capture module adds minimal overhead per captured hook invocation;\u003Cbr \u002F>\ndisable capturing on production when not actively debugging.\u003C\u002Fli>\n\u003Cli>The URL Tracker records page visits in a custom table; configure retention\u003Cbr \u002F>\nor pause tracking on high-traffic sites.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Support & Notes\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Secure log paths and consider randomising filenames in production.\u003C\u002Fli>\n\u003Cli>Disable unused modules to reduce footprint and attack surface.\u003C\u002Fli>\n\u003Cli>Recovery Mode has limitations on multisite — test before relying on it.\u003C\u002Fli>\n\u003Cli>For bugs or feature requests, open an issue on the plugin page.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Live preview and full details:\u003Cbr \u002F>\nhttps:\u002F\u002Fwordpress.org\u002Fplugins\u002F0-day-analytics\u002F\u003C\u002Fp>\n\u003Cp>Plugin website and documentation:\u003Cbr \u002F>\nhttps:\u002F\u002F0-day-analytics.com\u003C\u002Fp>\n","0 Day Analytics is a comprehensive WordPress debugging and operational",40,5961,"2026-04-06T08:45:00.000Z","6.0","7.4",[158,4,21,159,160],"cron","performance","transients","https:\u002F\u002F0-day-analytics.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002F0-day-analytics.5.0.0.zip","2025-11-12 00:00:00",{"attackSurface":165,"codeSignals":186,"taintFlows":193,"riskAssessment":194,"analyzedAt":202},{"hooks":166,"ajaxHandlers":182,"restRoutes":183,"shortcodes":184,"cronEvents":185,"entryPointCount":28,"unprotectedCount":28},[167,173,178],{"type":168,"name":169,"callback":170,"file":171,"line":172},"action","admin_init","debug_handle_file_download","functions\\function.php",219,{"type":168,"name":174,"callback":175,"file":176,"line":177},"admin_menu","debug_admin_menu","functions\\plugin.php",12,{"type":168,"name":179,"callback":180,"file":176,"line":181},"init","debug_send_notification_email",45,[],[],[],[],{"dangerousFunctions":187,"sqlUsage":188,"outputEscaping":190,"fileOperations":114,"externalRequests":28,"nonceChecks":114,"capabilityChecks":28,"bundledLibraries":192},[],{"prepared":28,"raw":28,"locations":189},[],{"escaped":28,"rawEcho":28,"locations":191},[],[],[],{"summary":195,"deductions":196},"The 'debug' v1.12 plugin exhibits a generally strong security posture based on the static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events with unprotected entry points is a significant positive, indicating a minimal attack surface. The code also demonstrates good practices by utilizing prepared statements for all SQL queries and properly escaping all outputs. The presence of nonces for its file operations further reinforces a commitment to preventing common web vulnerabilities.  \n\nHowever, the presence of file operations (3) without explicit capability checks raises a potential concern. While nonces are present, the lack of capability checks means that if a nonce is compromised or bypassed, the file operations could potentially be executed by any authenticated user, regardless of their privilege level. This could lead to unauthorized file manipulation if the file operations themselves are not inherently restricted. \n\nDespite the static analysis's clean bill of health in terms of taint flows and dangerous functions, the plugin's vulnerability history is a notable weakness. With one known CVE, specifically a medium severity CSRF vulnerability, it demonstrates that the plugin has had exploitable flaws in the past. While currently unpatched vulnerabilities are zero, the past occurrence of CSRF indicates that developers should remain vigilant about implementing robust protection mechanisms for any future administrative actions, even if they aren't directly exposed via AJAX or other common entry points. The overall security is good but the historical vulnerability and the lack of capability checks on file operations warrant attention.",[197,200],{"reason":198,"points":199},"File operations without capability checks",10,{"reason":201,"points":199},"Past medium severity CVE (CSRF)","2026-03-16T18:29:29.192Z",{"wat":204,"direct":213},{"assetPaths":205,"generatorPatterns":208,"scriptPaths":209,"versionParams":210},[206,207],"\u002Fwp-content\u002Fplugins\u002Fdebug\u002Ffunctions\u002Ffunction.php","\u002Fwp-content\u002Fplugins\u002Fdebug\u002Ffunctions\u002Fplugin.php",[],[],[211,212],"debug\u002Fstyle.css?ver=","debug\u002Fscript.js?ver=",{"cssClasses":214,"htmlComments":215,"htmlAttributes":216,"restEndpoints":217,"jsGlobals":218,"shortcodeOutput":219},[],[],[],[],[],[],{"error":221,"url":222,"statusCode":223,"statusMessage":224,"message":224},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fdebug\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":226,"versions":227},13,[228,233,239,247,255,263,271,279,287,295,303,311,319],{"version":6,"download_url":25,"svn_tag_url":229,"released_at":38,"has_diff":50,"diff_files_changed":230,"diff_lines":38,"trac_diff_url":231,"vulnerabilities":232,"is_current":221},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug\u002Ftags\u002F1.12\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug%2Ftags%2F1.11&new_path=%2Fdebug%2Ftags%2F1.12",[],{"version":40,"download_url":234,"svn_tag_url":235,"released_at":38,"has_diff":50,"diff_files_changed":236,"diff_lines":38,"trac_diff_url":237,"vulnerabilities":238,"is_current":50},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug.1.11.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug\u002Ftags\u002F1.11\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug%2Ftags%2F1.10&new_path=%2Fdebug%2Ftags%2F1.11",[],{"version":240,"download_url":241,"svn_tag_url":242,"released_at":38,"has_diff":50,"diff_files_changed":243,"diff_lines":38,"trac_diff_url":244,"vulnerabilities":245,"is_current":50},"1.10","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug.1.10.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug\u002Ftags\u002F1.10\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug%2Ftags%2F1.9&new_path=%2Fdebug%2Ftags%2F1.10",[246],{"id":34,"url_slug":35,"title":36,"severity":41,"cvss_score":42,"vuln_type":44,"patched_in_version":40},{"version":248,"download_url":249,"svn_tag_url":250,"released_at":38,"has_diff":50,"diff_files_changed":251,"diff_lines":38,"trac_diff_url":252,"vulnerabilities":253,"is_current":50},"1.9","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug.1.9.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug\u002Ftags\u002F1.9\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug%2Ftags%2F1.8&new_path=%2Fdebug%2Ftags%2F1.9",[254],{"id":34,"url_slug":35,"title":36,"severity":41,"cvss_score":42,"vuln_type":44,"patched_in_version":40},{"version":256,"download_url":257,"svn_tag_url":258,"released_at":38,"has_diff":50,"diff_files_changed":259,"diff_lines":38,"trac_diff_url":260,"vulnerabilities":261,"is_current":50},"1.8","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug.1.8.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug\u002Ftags\u002F1.8\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug%2Ftags%2F1.7&new_path=%2Fdebug%2Ftags%2F1.8",[262],{"id":34,"url_slug":35,"title":36,"severity":41,"cvss_score":42,"vuln_type":44,"patched_in_version":40},{"version":264,"download_url":265,"svn_tag_url":266,"released_at":38,"has_diff":50,"diff_files_changed":267,"diff_lines":38,"trac_diff_url":268,"vulnerabilities":269,"is_current":50},"1.7","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug.1.7.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug\u002Ftags\u002F1.7\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug%2Ftags%2F1.6&new_path=%2Fdebug%2Ftags%2F1.7",[270],{"id":34,"url_slug":35,"title":36,"severity":41,"cvss_score":42,"vuln_type":44,"patched_in_version":40},{"version":272,"download_url":273,"svn_tag_url":274,"released_at":38,"has_diff":50,"diff_files_changed":275,"diff_lines":38,"trac_diff_url":276,"vulnerabilities":277,"is_current":50},"1.6","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug.1.6.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug\u002Ftags\u002F1.6\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug%2Ftags%2F1.5&new_path=%2Fdebug%2Ftags%2F1.6",[278],{"id":34,"url_slug":35,"title":36,"severity":41,"cvss_score":42,"vuln_type":44,"patched_in_version":40},{"version":280,"download_url":281,"svn_tag_url":282,"released_at":38,"has_diff":50,"diff_files_changed":283,"diff_lines":38,"trac_diff_url":284,"vulnerabilities":285,"is_current":50},"1.5","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug.1.5.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug\u002Ftags\u002F1.5\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug%2Ftags%2F1.4&new_path=%2Fdebug%2Ftags%2F1.5",[286],{"id":34,"url_slug":35,"title":36,"severity":41,"cvss_score":42,"vuln_type":44,"patched_in_version":40},{"version":288,"download_url":289,"svn_tag_url":290,"released_at":38,"has_diff":50,"diff_files_changed":291,"diff_lines":38,"trac_diff_url":292,"vulnerabilities":293,"is_current":50},"1.4","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug.1.4.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug\u002Ftags\u002F1.4\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug%2Ftags%2F1.3&new_path=%2Fdebug%2Ftags%2F1.4",[294],{"id":34,"url_slug":35,"title":36,"severity":41,"cvss_score":42,"vuln_type":44,"patched_in_version":40},{"version":296,"download_url":297,"svn_tag_url":298,"released_at":38,"has_diff":50,"diff_files_changed":299,"diff_lines":38,"trac_diff_url":300,"vulnerabilities":301,"is_current":50},"1.3","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug.1.3.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug\u002Ftags\u002F1.3\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug%2Ftags%2F1.2&new_path=%2Fdebug%2Ftags%2F1.3",[302],{"id":34,"url_slug":35,"title":36,"severity":41,"cvss_score":42,"vuln_type":44,"patched_in_version":40},{"version":304,"download_url":305,"svn_tag_url":306,"released_at":38,"has_diff":50,"diff_files_changed":307,"diff_lines":38,"trac_diff_url":308,"vulnerabilities":309,"is_current":50},"1.2","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug.1.2.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug\u002Ftags\u002F1.2\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug%2Ftags%2F1.1&new_path=%2Fdebug%2Ftags%2F1.2",[310],{"id":34,"url_slug":35,"title":36,"severity":41,"cvss_score":42,"vuln_type":44,"patched_in_version":40},{"version":312,"download_url":313,"svn_tag_url":314,"released_at":38,"has_diff":50,"diff_files_changed":315,"diff_lines":38,"trac_diff_url":316,"vulnerabilities":317,"is_current":50},"1.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug.1.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug\u002Ftags\u002F1.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdebug%2Ftags%2F1.0&new_path=%2Fdebug%2Ftags%2F1.1",[318],{"id":34,"url_slug":35,"title":36,"severity":41,"cvss_score":42,"vuln_type":44,"patched_in_version":40},{"version":320,"download_url":321,"svn_tag_url":322,"released_at":38,"has_diff":50,"diff_files_changed":323,"diff_lines":38,"trac_diff_url":38,"vulnerabilities":324,"is_current":50},"1.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug.1.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdebug\u002Ftags\u002F1.0\u002F",[],[325],{"id":34,"url_slug":35,"title":36,"severity":41,"cvss_score":42,"vuln_type":44,"patched_in_version":40}]