[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fJspf51njrEMI4y8s4wlVyScin4bUIKGVSRBo9qhM-jo":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":25,"download_link":26,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29,"vulnerabilities":30,"developer":31,"crawl_stats":28,"alternatives":36,"analysis":130,"fingerprints":287},"debug-log-tool","BugTrace – Debug Log Tool","1.0.7","Nikhil G","https:\u002F\u002Fprofiles.wordpress.org\u002Fnsgawli\u002F","\u003Cp>Tired of cumbersome debugging processes? BugTrace – Debug Log Tool streamlines WordPress troubleshooting, providing developers and site administrators with a powerful yet minimalist interface to diagnose and resolve issues swiftly. Stop wasting time with manual wp-config.php edits or FTP access for basic debugging tasks.\u003C\u002Fp>\n\u003Cp>With BugTrace, you can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Instantly Control Debug Constants:\u003C\u002Fstrong> Gain immediate access to toggle crucial WordPress debugging constants like WP_DEBUG, WP_DEBUG_LOG, WP_DEBUG_DISPLAY, and SCRIPT_DEBUG directly from your dashboard. Activate or deactivate them with a single click—no code editing required, saving you valuable development time and reducing the risk of site-breaking syntax errors.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>AI-Powered Error Resolution (ChatGPT, Gemini & Google):\u003C\u002Fstrong> Stop guessing and start solving! For every log entry, BugTrace provides one-click ‘Help’ links. Instantly send the error message to ChatGPT, Gemini, or Google to find solutions, code snippets, and explanations. Drastically reduce your troubleshooting time and solve complex problems faster than ever before.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Effortlessly Access Debug Logs:\u003C\u002Fstrong> View and download your WordPress \u003Ccode>debug.log\u003C\u002Fcode> file directly from the admin panel. This allows for quick identification of PHP errors, warnings, and notices, helping you pinpoint the source of problems much faster than traditional methods.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Dynamic Log Viewing with Auto & Manual Refresh:\u003C\u002Fstrong> Keep an eye on your \u003Ccode>debug.log\u003C\u002Fcode> in near real-time with the auto-refresh option, or manually refresh the log view whenever you need. This helps in actively monitoring errors as they occur and is invaluable for live debugging sessions.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Securely Inspect Server Configurations:\u003C\u002Fstrong> Safely view the contents of vital server files such as \u003Ccode>.htaccess\u003C\u002Fcode> and wp-config.php (read-only), and review detailed \u003Ccode>phpinfo()\u003C\u002Fcode> output without ever leaving your WordPress environment. This provides essential insights for advanced WordPress troubleshooting and server diagnostics.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Monitor Key System Behaviors:\u003C\u002Fstrong> Get a clear overview of your database table information (including size and row count), view active browser cookies (read-only), inspect WordPress transients (read-only), and check your list of scheduled WordPress cron jobs. This comprehensive visibility helps you understand your site’s inner workings.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Utilize Admin Bar Shortcuts:\u003C\u002Fstrong> Speed up your debugging workflow with convenient admin bar shortcuts to view, download, and clear the \u003Ccode>debug.log\u003C\u002Fcode> file from anywhere in your WordPress admin area.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Quick Log to Clipboard:\u003C\u002Fstrong> Instantly copy the entire contents of your log to your clipboard with a single click. Perfect for quickly sharing log details with support teams, pasting into development tools, or for your own records.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enjoy a Minimalist Interface:\u003C\u002Fstrong> BugTrace is intentionally lightweight with a clean UI, focusing purely on essential debugging tools to ensure it doesn’t bog down your WordPress site.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Whether you’re developing a new theme or plugin, troubleshooting a tricky bug on a staging server, or performing routine site health checks, BugTrace – Debug Log Tool provides the critical information you need, efficiently and effectively.\u003C\u002Fp>\n","Essential WordPress debug tool: View\u002Fdownload logs, toggle debug settings & inspect server info. Troubleshoot PHP errors & site issues faster!",40,887,100,1,"2025-12-07T12:40:00.000Z","6.9.4","6.2","7.4",[20,21,22,23,24],"database-info","debug-log","php-errors","troubleshooting-tool","wordpress-debug","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug-log-tool.1.0.7.zip",0,null,"2026-03-15T15:16:48.613Z",[],{"slug":32,"display_name":7,"profile_url":8,"plugin_count":14,"total_installs":11,"avg_security_score":13,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"nsgawli",30,94,"2026-04-04T09:59:31.002Z",[37,57,79,98,114],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":13,"downloaded":45,"rating":46,"num_ratings":47,"last_updated":48,"tested_up_to":16,"requires_at_least":49,"requires_php":50,"tags":51,"homepage":25,"download_link":56,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"conflict-finder-wp-fix-it","Conflict Finder","7.2","WP Fix It - WordPress Experts","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpfixit\u002F","\u003Cp>Conflict Finder is a comprehensive troubleshooting plugin designed for WordPress administrators, developers, and support professionals who need to identify the root cause of site issues.\u003C\u002Fp>\n\u003Cp>From a single interface, Conflict Finder allows you to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enable and manage WP_DEBUG without manually editing files\u003C\u002Fli>\n\u003Cli>View, download, and clear the WordPress debug log\u003C\u002Fli>\n\u003Cli>Temporarily disable plugins to identify conflicts\u003C\u002Fli>\n\u003Cli>Switch themes to test theme-related issues\u003C\u002Fli>\n\u003Cli>Test WordPress email delivery using \u003Ccode>wp_mail()\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Important:\u003C\u002Fstrong>\u003Cbr \u002F>\nConflict Finder \u003Cstrong>does temporarily affect site behavior\u003C\u002Fstrong> while troubleshooting is active. This may include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Disabled plugins\u003C\u002Fli>\n\u003Cli>A different active theme\u003C\u002Fli>\n\u003Cli>Debug notices or errors being displayed\u003C\u002Fli>\n\u003Cli>Changes visible to logged-out visitors\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For this reason, troubleshooting should be performed during maintenance windows or on staging sites whenever possible.\u003C\u002Fp>\n\u003Cp>Conflict Finder automatically tracks your original configuration and allows you to restore plugins, themes, and debugging settings once testing is complete.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Troubleshooting Dashboard\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Central overview of debugging and conflict states\u003C\u002Fli>\n\u003Cli>Environment snapshot including WordPress, PHP, memory, and server software\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>WP_DEBUG Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enable or disable WP_DEBUG with a single switch\u003C\u002Fli>\n\u003Cli>Control error display and logging behavior\u003C\u002Fli>\n\u003Cli>Load unminified scripts for debugging\u003C\u002Fli>\n\u003Cli>View, download, or clear \u003Ccode>wp-content\u002Fdebug.log\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Safely updates \u003Ccode>wp-config.php\u003C\u002Fcode> as needed\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Plugin Conflict Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Temporarily deactivate all active plugins\u003C\u002Fli>\n\u003Cli>Save and restore original plugin states\u003C\u002Fli>\n\u003Cli>Activate plugins one at a time to identify conflicts\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Theme Conflict Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Temporarily switch to another installed theme\u003C\u002Fli>\n\u003Cli>Identify theme-related layout or functionality issues\u003C\u002Fli>\n\u003Cli>Restore the original theme instantly\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Email Delivery Tool\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Send a real test email using WordPress mail\u003C\u002Fli>\n\u003Cli>Confirm whether the server can successfully send email\u003C\u002Fli>\n\u003Cli>Helps identify SMTP or hosting mail issues\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>When to Use Conflict Finder\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Diagnosing white screens or fatal errors\u003C\u002Fli>\n\u003Cli>Identifying plugin conflicts\u003C\u002Fli>\n\u003Cli>Testing theme-related layout or functionality issues\u003C\u002Fli>\n\u003Cli>Investigating PHP notices or warnings\u003C\u002Fli>\n\u003Cli>Verifying WordPress email delivery\u003C\u002Fli>\n\u003Cli>Support and development workflows\u003C\u002Fli>\n\u003C\u002Ful>\n","Conflict Finder is a WordPress troubleshooting toolkit that helps diagnose plugin conflicts, theme issues, debugging errors, and email delivery proble &hellip;",8747,90,4,"2026-01-27T14:26:00.000Z","4.9","5.6",[21,52,53,54,55],"plugin-conflict","theme-conflict","troubleshooting","wp_debug","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fconflict-finder-wp-fix-it.7.2.zip",{"slug":58,"name":59,"version":60,"author":61,"author_profile":62,"description":63,"short_description":64,"active_installs":13,"downloaded":65,"rating":13,"num_ratings":66,"last_updated":67,"tested_up_to":68,"requires_at_least":69,"requires_php":50,"tags":70,"homepage":76,"download_link":77,"security_score":78,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"premmerce-dev-tools","Premmerce Dev Tools","2.0","Premmerce","https:\u002F\u002Fprofiles.wordpress.org\u002Fpremmerce\u002F","\u003Cp>This plugin is aimed at making it easier to develop, test and debug the code on the WordPress platform.\u003Cbr \u002F>\nWe created this plugin based on our research: \u003Ca href=\"https:\u002F\u002Fpremmerce.com\u002Fwordpress-development-environment-developers-best-practices-review\u002F\" rel=\"nofollow ugc\">WordPress Development Environment and Developers Best Practices Review\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Major features in “Premmerce Dev Tools”\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Integration of symfony\u002Fvar-dumper for debugging the code\u003C\u002Fli>\n\u003Cli>Integration symfony\u002Fstopwatch for the execution time checking\u003C\u002Fli>\n\u003Cli>Generating the test data for WooCommerce\u003C\u002Fli>\n\u003Cli>Plugin generator, which creates the basic files structure\u003C\u002Fli>\n\u003Cli>Database clean up\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Compatibility with other Plugins\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WooCommerce\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Installation\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Unzip the downloaded zip file.\u003C\u002Fli>\n\u003Cli>Upload the plugin folder into the ‘wp-content\u002Fplugins\u002F’ directory of your WordPress site.\u003C\u002Fli>\n\u003Cli>Activate ‘Premmerce Dev Tools’ from Plugins page\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Documentation\u003C\u002Fh3>\n\u003Cp>Full documentation is available here: \u003Ca href=\"https:\u002F\u002Fpremmerce.com\u002Fpremmerce-dev-tools\u002F\" rel=\"nofollow ugc\">Premmerce Dev Tools\u003C\u002Fa>\u003C\u002Fp>\n","This plugin is created to facilitate the development, testing and debugging of the code on the WordPress platform and to quickly create the demo data  &hellip;",5474,2,"2019-05-29T10:08:00.000Z","5.2.24","4.8",[71,72,73,74,75],"code-debug","debugging","developers-tools","plugin-generator","wordpress-debugging","https:\u002F\u002Fpremmerce.com\u002Fpremmerce-dev-tools\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpremmerce-dev-tools.2.0.zip",85,{"slug":80,"name":81,"version":82,"author":83,"author_profile":84,"description":85,"short_description":86,"active_installs":33,"downloaded":87,"rating":27,"num_ratings":27,"last_updated":88,"tested_up_to":16,"requires_at_least":89,"requires_php":89,"tags":90,"homepage":96,"download_link":97,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"eligibility-checklist-for-adsense","Eligibility Checklist for AdSense","3.0.2","mimusjobs","https:\u002F\u002Fprofiles.wordpress.org\u002Fmimusjobs\u002F","\u003Cp>**Eligibility Checklist for AdSense is a complete AdSense readiness and policy scanner designed to help site owners get approved faster and avoid policy violations.\u003C\u002Fp>\n\u003Cp>This plugin performs a \u003Cstrong>deep audit\u003C\u002Fstrong> of your site using:\u003Cbr \u002F>\n– External keyword lists (GitHub profanity, adult, and harmful content lists)\u003Cbr \u002F>\n– Content length + duplication checks\u003Cbr \u002F>\n– Thin content detection\u003Cbr \u002F>\n– Page structure audits (H1\u002FH2, essential pages, navigation)\u003Cbr \u002F>\n– Mobile friendliness checks\u003Cbr \u002F>\n– SEO visibility + indexability checks\u003Cbr \u002F>\n– Policy risk scoring and warnings\u003C\u002Fp>\n\u003Cp>You also get \u003Cstrong>Fix buttons\u003C\u002Fstrong>, remediation guides, and optional premium services (full PDF report, article packages, content optimization).\u003C\u002Fp>\n\u003Ch3>🔥 Key Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Full AdSense readiness score (0–100)\u003C\u002Fli>\n\u003Cli>Essential pages detection (Home, About, Contact, Privacy Policy)\u003C\u002Fli>\n\u003Cli>Duplicate content + partial plagiarism heuristics\u003C\u002Fli>\n\u003Cli>AI\u002Fspun content risk scoring\u003C\u002Fli>\n\u003Cli>Page-level word count audits\u003C\u002Fli>\n\u003Cli>Image audit (alt text presence)\u003C\u002Fli>\n\u003Cli>H1\u002FH2 structure scan\u003C\u002Fli>\n\u003Cli>Mobile-friendly test link\u003C\u002Fli>\n\u003Cli>Sitemap, robots, canonical, and indexability checks\u003C\u002Fli>\n\u003Cli>Re-run audit using AJAX (instant)\u003C\u002Fli>\n\u003Cli>Monetized service cards:\n\u003Cul>\n\u003Cli>$10 full PDF audit report\u003C\u002Fli>\n\u003Cli>$50 article bundle + site optimization\u003C\u002Fli>\n\u003Cli>$1\u002Farticle human-written custom content\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Why This Plugin Exists\u003C\u002Fh3>\n\u003Cp>AdSense approvals in 2025 require stronger content quality, page trust indicators, and consistent site structure. Many site owners fail due to missing pages or thin content.\u003Cbr \u002F>\nThis plugin solves that by providing a \u003Cstrong>one-page dashboard\u003C\u002Fstrong> showing everything Google expects from a compliant site.\u003C\u002Fp>\n","A full AdSense approval & policy audit dashboard for 2025. Scans your site using external keyword lists, content heuristics, and policy checks — w &hellip;",268,"2025-12-06T21:01:00.000Z","5.0",[91,92,93,94,95],"adsense-policy-compliance-checker","adsense-rejection-troubleshooting-tool","adsense-site-audit-and-analysis","google-adsense-approval-checklist-2026","google-adsense-content-quality-audit","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Feligibility-checklist-for-adsense","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Feligibility-checklist-for-adsense.zip",{"slug":99,"name":100,"version":101,"author":102,"author_profile":103,"description":104,"short_description":105,"active_installs":106,"downloaded":107,"rating":27,"num_ratings":27,"last_updated":108,"tested_up_to":16,"requires_at_least":109,"requires_php":50,"tags":110,"homepage":112,"download_link":113,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"change-debug-log-location","Change Debug Log Location","0.0.2","Jose Mortellaro","https:\u002F\u002Fprofiles.wordpress.org\u002Fgiuse\u002F","\u003Cp>Normally, if the debug is active, the file debug.log is included in the folder wp-content, and everybody can read it at https:\u002F\u002Fyour-domain.com\u002Fwp-content\u002Fdebug.log\u002F.\u003C\u002Fp>\n\u003Cp>Activating Change Debug Log Location you will find the debug.log file in the main directory, but it will have a name that looks like debug-6583fb9c.log.\u003C\u002Fp>\n\u003Cp>So only those who know the name will be able to find it.\u003C\u002Fp>\n\u003Cp>Deactivating the plugin it will not delete the debug file, because we don’t want you lose any information, of course you can delete it manually via FTP.\u003C\u002Fp>\n\u003Cp>Moreover, after deactivating the plugin the debug will be disabled. If you need it, you should enable it again in wp-config.php.\u003C\u002Fp>\n\u003Cp>Of course, if the debug is disabled because you don’t need it (the default of WordPress), you also don’t need this plugin. This plugin is only for those who need to read the debug.log file, but they don’t want everybody can read it.\u003C\u002Fp>\n\u003Ch3>Help\u003C\u002Fh3>\n\u003Cp>If you need help open a thread on the support forum of this plugin.\u003Cbr \u002F>\nPlease, before posting enable the debugging in wp-config.php. Need a step-by-step guide? Read \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Fhow-to-enable-debugging-in-wordpress-a-step-by-step-guide\u002F\" rel=\"nofollow ugc\">this detailed tutorial\u003C\u002Fa> on \u003Ca href=\"https:\u002F\u002Ffreesoul-deactivate-plugins.com\u002Fhow-to-enable-debugging-in-wordpress-a-step-by-step-guide\u002F\" rel=\"nofollow ugc\">how to enable debugging in WordPress\u003C\u002Fa> to learn more.\u003C\u002Fp>\n","Your website will not send any email in case of fatal errors.",10,1887,"2025-12-05T08:46:00.000Z","4.6",[111],"it-changes-the-title-and-the-location-of-the-file-debug-log","https:\u002F\u002Fjosemortellaro.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fchange-debug-log-location.0.0.2.zip",{"slug":115,"name":116,"version":117,"author":118,"author_profile":119,"description":120,"short_description":121,"active_installs":106,"downloaded":122,"rating":27,"num_ratings":27,"last_updated":25,"tested_up_to":123,"requires_at_least":124,"requires_php":25,"tags":125,"homepage":127,"download_link":128,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":129},"clear-debuglog-cron","Clear Debug.log Cron","0.1","salocined","https:\u002F\u002Fprofiles.wordpress.org\u002Fsalocined\u002F","\u003Cp>This plugin will automatically delete the debug.log file generated by WordPress in wp-content.\u003Cbr \u002F>\nThe plugin will run every hour.\u003Cbr \u002F>\nThere is no administration area but the code is clear and clean and the plugin can be easily modified for your need.\u003C\u002Fp>\n\u003Ch3>Arbitrary section\u003C\u002Fh3>\n\u003Ch3>A brief Markdown Example\u003C\u002Fh3>\n","This plugin will automatically delete the debug.log file generated by Wordpress in wp-content.",1875,"3.5.2","3.4",[126,21],"cron","http:\u002F\u002Fwww.wpsupprt.co.uk","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fclear-debuglog-cron.zip","2026-03-15T10:48:56.248Z",{"attackSurface":131,"codeSignals":199,"taintFlows":222,"riskAssessment":278,"analyzedAt":286},{"hooks":132,"ajaxHandlers":176,"restRoutes":195,"shortcodes":196,"cronEvents":197,"entryPointCount":198,"unprotectedCount":27},[133,139,144,148,153,155,159,163,167,169,173],{"type":134,"name":135,"callback":136,"priority":13,"file":137,"line":138},"action","admin_bar_menu","add_admin_bar_menu","includes\\admin\\class-wpdt-admin-bar-menu.php",15,{"type":134,"name":140,"callback":141,"file":142,"line":143},"admin_enqueue_scripts","load_scripts","includes\\admin\\class-wpdt-admin.php",17,{"type":134,"name":145,"callback":146,"priority":106,"file":142,"line":147},"admin_menu","load_admin_menus",18,{"type":134,"name":149,"callback":150,"file":151,"line":152},"wpdt_save_general_settings","set_debug_constants","includes\\admin\\settings\\class-wpdt-config-manager.php",16,{"type":134,"name":154,"callback":150,"file":151,"line":143},"wpdt_reset_general_settings",{"type":134,"name":156,"callback":157,"file":151,"line":158},"wpdt_activation","activate",20,{"type":134,"name":160,"callback":161,"file":151,"line":162},"wpdt_deactivation","deactivate",21,{"type":134,"name":164,"callback":165,"priority":13,"file":166,"line":143},"init","download_debug_file","includes\\admin\\settings\\class-wpdt-logs.php",{"type":134,"name":164,"callback":168,"priority":13,"file":166,"line":147},"reset_debug_file",{"type":134,"name":164,"callback":170,"priority":14,"file":171,"line":172},"initial_setup","includes\\class-wpdt-installation.php",47,{"type":134,"name":164,"callback":174,"priority":14,"file":171,"line":175},"upgrade",49,[177,182,186,190,193],{"action":178,"nopriv":179,"callback":180,"hasNonce":181,"hasCapCheck":179,"file":166,"line":162},"wpdt_get_debug_logs",false,"get_debug_logs",true,{"action":183,"nopriv":179,"callback":184,"hasNonce":181,"hasCapCheck":179,"file":166,"line":185},"wpdt_set_auto_refresh","set_auto_refresh",24,{"action":187,"nopriv":179,"callback":188,"hasNonce":181,"hasCapCheck":179,"file":166,"line":189},"wpdt_set_group_logs","set_group_logs",27,{"action":149,"nopriv":179,"callback":191,"hasNonce":181,"hasCapCheck":179,"file":192,"line":147},"save_general_settings","includes\\admin\\settings\\class-wpdt-settings.php",{"action":154,"nopriv":179,"callback":194,"hasNonce":181,"hasCapCheck":179,"file":192,"line":162},"reset_general_settings",[],[],[],5,{"dangerousFunctions":200,"sqlUsage":201,"outputEscaping":204,"fileOperations":217,"externalRequests":14,"nonceChecks":217,"capabilityChecks":27,"bundledLibraries":218},[],{"prepared":202,"raw":27,"locations":203},11,[],{"escaped":205,"rawEcho":206,"locations":207},86,3,[208,212,214],{"file":209,"line":210,"context":211},"includes\\admin\\settings\\class-wpdt-helper.php",19,"raw output",{"file":166,"line":213,"context":211},140,{"file":215,"line":216,"context":211},"includes\\admin\\settings\\class-wpdt-server-info.php",330,8,[219],{"name":220,"version":28,"knownCves":221},"DataTables",[],[223,241,251,260,270],{"entryPoint":224,"graph":225,"unsanitizedCount":27,"severity":240},"set_auto_refresh (includes\\admin\\settings\\class-wpdt-logs.php:272)",{"nodes":226,"edges":238},[227,232],{"id":228,"type":229,"label":230,"file":166,"line":231},"n0","source","$_POST",278,{"id":233,"type":234,"label":235,"file":166,"line":236,"wp_function":237},"n1","sink","update_option() [Settings Manipulation]",279,"update_option",[239],{"from":228,"to":233,"sanitized":181},"low",{"entryPoint":242,"graph":243,"unsanitizedCount":27,"severity":240},"set_group_logs (includes\\admin\\settings\\class-wpdt-logs.php:288)",{"nodes":244,"edges":249},[245,247],{"id":228,"type":229,"label":230,"file":166,"line":246},294,{"id":233,"type":234,"label":235,"file":166,"line":248,"wp_function":237},295,[250],{"from":228,"to":233,"sanitized":181},{"entryPoint":252,"graph":253,"unsanitizedCount":27,"severity":240},"\u003Cclass-wpdt-logs> (includes\\admin\\settings\\class-wpdt-logs.php:0)",{"nodes":254,"edges":258},[255,257],{"id":228,"type":229,"label":256,"file":166,"line":231},"$_POST (x2)",{"id":233,"type":234,"label":235,"file":166,"line":236,"wp_function":237},[259],{"from":228,"to":233,"sanitized":181},{"entryPoint":261,"graph":262,"unsanitizedCount":27,"severity":240},"save_general_settings (includes\\admin\\settings\\class-wpdt-settings.php:121)",{"nodes":263,"edges":268},[264,266],{"id":228,"type":229,"label":230,"file":192,"line":265},138,{"id":233,"type":234,"label":235,"file":192,"line":267,"wp_function":237},142,[269],{"from":228,"to":233,"sanitized":181},{"entryPoint":271,"graph":272,"unsanitizedCount":27,"severity":240},"\u003Cclass-wpdt-settings> (includes\\admin\\settings\\class-wpdt-settings.php:0)",{"nodes":273,"edges":276},[274,275],{"id":228,"type":229,"label":256,"file":192,"line":265},{"id":233,"type":234,"label":235,"file":192,"line":267,"wp_function":237},[277],{"from":228,"to":233,"sanitized":181},{"summary":279,"deductions":280},"The 'debug-log-tool' plugin v1.0.7 exhibits a generally strong security posture, primarily due to its diligent use of prepared statements for SQL queries and a high percentage of properly escaped output. The static analysis reveals no critical or high-severity taint flows, and the plugin has no recorded vulnerability history, suggesting a well-maintained codebase.\n\nHowever, the analysis does highlight areas for improvement. While all AJAX handlers have authentication checks, the absence of capability checks is a concern. This means that any authenticated user, regardless of their role or permissions, could potentially interact with these AJAX endpoints. The plugin also bundles the DataTables library, and while its version isn't specified, outdated bundled libraries can introduce vulnerabilities if not kept current. The presence of file operations and external HTTP requests, while not inherently insecure, requires careful scrutiny to ensure they are not mishandled.\n\nIn conclusion, the plugin is built on a foundation of good security practices, particularly regarding data handling. The main weaknesses lie in the potential for privilege escalation through AJAX endpoints without granular capability checks and the implicit risk associated with bundled libraries. Addressing these points would further solidify its security.",[281,284],{"reason":282,"points":283},"AJAX handlers without capability checks",7,{"reason":285,"points":206},"Bundled library (DataTables) - version unknown","2026-03-16T22:19:47.252Z",{"wat":288,"direct":303},{"assetPaths":289,"generatorPatterns":295,"scriptPaths":296,"versionParams":297},[290,291,292,293,294],"\u002Fwp-content\u002Fplugins\u002Fdebug-log-tool\u002Fasset\u002Fjs\u002Fadmin.js","\u002Fwp-content\u002Fplugins\u002Fdebug-log-tool\u002Fasset\u002Fcss\u002Fadmin-rtl.css","\u002Fwp-content\u002Fplugins\u002Fdebug-log-tool\u002Fasset\u002Fcss\u002Fadmin.css","\u002Fwp-content\u002Fplugins\u002Fdebug-log-tool\u002Fasset\u002Flib\u002FDataTables\u002Fdatatables.min.js","\u002Fwp-content\u002Fplugins\u002Fdebug-log-tool\u002Fasset\u002Flib\u002FDataTables\u002Fdatatables.min.css",[],[290,293],[298,299,300,301,302],"debug-log-tool\u002Fasset\u002Fjs\u002Fadmin.js?ver=","debug-log-tool\u002Fasset\u002Fcss\u002Fadmin-rtl.css?ver=","debug-log-tool\u002Fasset\u002Fcss\u002Fadmin.css?ver=","debug-log-tool\u002Fasset\u002Flib\u002FDataTables\u002Fdatatables.min.js?ver=","debug-log-tool\u002Fasset\u002Flib\u002FDataTables\u002Fdatatables.min.css?ver=",{"cssClasses":304,"htmlComments":310,"htmlAttributes":311,"restEndpoints":314,"jsGlobals":315,"shortcodeOutput":317},[305,306,307,308,309],"wpdt-header","wpdt-header-title","wpdt-header-icon","wpdt-header-buttons","wpdt-button",[],[312,313],"data-nonce","data-home_url",[],[316],"wpdebugtool",[]]