[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fgirUKKY1G64vFh5txzJwVYLOVL-JoV851eibkFmB1jc":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":37,"analysis":141,"fingerprints":287},"simple-log-viewer","Simple Log Viewer","1.0.4","Pedro Avelar","https:\u002F\u002Fprofiles.wordpress.org\u002Fpedroasa\u002F","\u003Cp>A simple plugin to log errors in real time in a metabox in the admin panel, too integrated with WP-CLI.\u003C\u002Fp>\n\u003Cp>For the run command with WP-CLI is necessary to activate the plugin and install WP-CLI.\u003C\u002Fp>\n\u003Cp>When running, paste the command \u003Ccode>wp slvpl logs-erros\u003C\u002Fcode> into the terminal, by default the number of lines is 1000 but you can control the number of lines through the \u003Ccode>--num_linhas\u003C\u002Fcode> parameter\u003C\u002Fp>\n\u003Cp>\u003Cstrong>For the example\u003C\u002Fstrong>:  \u003Ccode>wp slvpl logs-erros [--num_linhas=\u003Cnum_linhas>]\u003C\u002Fcode> or\u003Cbr \u002F>\nbetter in the example \u003Ccode>wp slvpl logs-erros --num_linhas=100\u003C\u002Fcode>.\u003C\u002Fp>\n","A simple plugin to log errors in real time in a metabox in the admin panel, too integrated with WP-CLI",10,1857,100,2,"2025-05-26T01:49:00.000Z","6.6.5","5.4","7.4",[20,21,22,23,24],"dashboard-widget","debug","error-reporting","erros","logs","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsimple-log-viewer.1.0.4.zip",0,null,"2026-03-15T15:16:48.613Z",[],{"slug":32,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":11,"avg_security_score":13,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},"pedroasa",1,30,94,"2026-04-03T19:34:36.728Z",[38,54,77,99,122],{"slug":39,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":11,"downloaded":46,"rating":13,"num_ratings":33,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":18,"tags":50,"homepage":25,"download_link":53,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"js-error-logger","JS Error Logger","1.3.1","JFG Media","https:\u002F\u002Fprofiles.wordpress.org\u002Fjfgmedia\u002F","\u003Cp>The plugin catches most JS errors, logs them, and displays them in a dashboard widget.\u003C\u002Fp>\n\u003Cp>Here are some of its features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\nExcept for the plugin settings, there is no database storage involved. Log is written in a “.log” file.\n\u003C\u002Fli>\n\u003Cli>\nDisplay latest JS errors in a dashboard widget.\n\u003C\u002Fli>\n\u003Cli>\nRefresh errors from the dashboard widget.\n\u003C\u002Fli>\n\u003Cli>\nSee the full error log on a separate page.\n\u003C\u002Fli>\n\u003Cli>\nIgnore errors if the user agent contains a specific string.\n\u003C\u002Fli>\n\u003Cli>\nIgnore errors if the error contains a specific string.\n\u003C\u002Fli>\n\u003Cli>\nIgnore errors if the script url contains a specific string.\n\u003C\u002Fli>\n\u003Cli>\nSee which page and which script triggered the errors.\n\u003C\u002Fli>\n\u003Cli>\nChoose the maximum amount of errors to log per page load.\n\u003C\u002Fli>\n\u003Cli>\nExclude logging errors from specific post types.\n\u003C\u002Fli>\n\u003Cli>\nChoose how ajax calls are made.\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Developer hooks and filters\u003C\u002Fh4>\n\u003Cp>The plugin cleans the log every 24 hours, to only keep the last 100 entries.\u003Cbr \u002F>\nYou may use the “jserrlog_max_log_entries” WP filter to enable more or less entries, by returning an integer: \u003Ccode>add_filter('jserrlog_max_log_entries',function(){return 200;})\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>Alter error data:\u003Cbr \u002F>\nYou may use the “jserrlog_pre_insert_error” WP filter to modify the error data before it’s inserted into the log file: \u003Ccode>add_filter('jserrlog_pre_insert_error',function($error_data){return $error_data;})\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>Trigger integrations:\u003Cbr \u002F>\nYou may use the “jserrlog_after_log” WP hook to trigger an action (Slack notification, etc.) after an error was logged: \u003Ccode>add_action('jserrlog_after_log',function($error_data){\u002F\u002Fdo something})\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>Backup old errors:\u003Cbr \u002F>\nYou may use the “jserrlog_before_log_maintenance” WP hook to trigger an action (archive errors, etc.) before old errors are deleted: \u003Ccode>add_action('jserrlog_before_log_maintenance',function($errors){\u002F\u002Fdo something})\u003C\u002Fcode>\u003C\u002Fp>\n\u003Ch4>Multisite\u003C\u002Fh4>\n\u003Cp>The plugin works with multisite. There’s one error log per site.\u003C\u002Fp>\n","Logs front-end javascript errors, and displays them in a dashboard widget",1446,"2025-12-11T05:34:00.000Z","6.9.4","5.0",[20,21,22,51,52],"javascript","js","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fjs-error-logger.1.3.1.zip",{"slug":55,"name":56,"version":57,"author":58,"author_profile":59,"description":60,"short_description":61,"active_installs":62,"downloaded":63,"rating":64,"num_ratings":65,"last_updated":66,"tested_up_to":67,"requires_at_least":68,"requires_php":18,"tags":69,"homepage":73,"download_link":74,"security_score":75,"vuln_count":33,"unpatched_count":27,"last_vuln_date":76,"fetched_at":29},"error-log-monitor","Error Log Monitor","1.7.12","Janis Elsts","https:\u002F\u002Fprofiles.wordpress.org\u002Fwhiteshadow\u002F","\u003Cp>This plugin adds a Dashboard widget that displays the latest messages from your PHP error log. It can also send you email notifications about newly logged errors.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Automatically detects error log location.\u003C\u002Fli>\n\u003Cli>Explains how to configure PHP error logging if it’s not enabled yet.\u003C\u002Fli>\n\u003Cli>The number of displayed log entries is configurable.\u003C\u002Fli>\n\u003Cli>Sends you email notifications about logged errors (optional).\u003C\u002Fli>\n\u003Cli>Configurable email address and frequency.\u003C\u002Fli>\n\u003Cli>You can easily clear the log file.\u003C\u002Fli>\n\u003Cli>The dashboard widget is only visible to administrators.\u003C\u002Fli>\n\u003Cli>Optimized to work well even with very large log files.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Usage\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Once you’ve installed the plugin, go to the Dashboard and enable the “PHP Error Log” widget through the “Screen Options” panel. The widget should automatically display the last 20 lines from your PHP error log. If you see an error message like “Error logging is disabled” instead, follow the displayed instructions to configure error logging.\u003C\u002Fp>\n\u003Cp>Email notifications are disabled by default. To enable them, click the “Configure” link in the top-right corner of the widget and enter your email address in the “Periodically email logged errors to:” box. If desired, you can also change email frequency by selecting the minimum time interval between emails from the “How often to send email” drop-down.\u003C\u002Fp>\n","Adds a Dashboard widget that displays the latest messages from your PHP error log. It can also send logged errors to email.",20000,631204,86,48,"2025-10-01T15:12:00.000Z","6.8.5","4.5",[70,71,20,22,72],"admin","administration","php","http:\u002F\u002Fw-shadow.com\u002Fblog\u002F2012\u002F07\u002F25\u002Ferror-log-monitor-plugin\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ferror-log-monitor.1.7.12.zip",99,"2019-02-25 00:00:00",{"slug":21,"name":78,"version":79,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":84,"downloaded":85,"rating":86,"num_ratings":87,"last_updated":88,"tested_up_to":89,"requires_at_least":90,"requires_php":91,"tags":92,"homepage":25,"download_link":96,"security_score":97,"vuln_count":33,"unpatched_count":27,"last_vuln_date":98,"fetched_at":29},"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,93492,92,11,"2024-04-01T14:15:00.000Z","6.4.8","3.4","5.6",[21,93,94,95,22],"display-error","error-log","error-notification","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebug.1.12.zip",85,"2024-01-31 00:00:00",{"slug":100,"name":101,"version":102,"author":103,"author_profile":104,"description":105,"short_description":106,"active_installs":107,"downloaded":108,"rating":109,"num_ratings":110,"last_updated":111,"tested_up_to":48,"requires_at_least":112,"requires_php":113,"tags":114,"homepage":118,"download_link":119,"security_score":120,"vuln_count":14,"unpatched_count":27,"last_vuln_date":121,"fetched_at":29},"decalog","DecaLog","4.5.0","Pierre Lannoy","https:\u002F\u002Fprofiles.wordpress.org\u002Fpierrelannoy\u002F","\u003Cp>\u003Cstrong>Capture and log events, metrics and traces on your site. Make WordPress observable – finally!\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>De-facto standard stack for WordPress observability, \u003Cstrong>DecaLog\u003C\u002Fstrong> provides reliable and powerful logging, monitoring and tracing features for WordPress core, PHP, database, plugins and themes.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>DecaLog\u003C\u002Fstrong> captures events generated by WordPress core, PHP, database, plugins and themes, collates metrics and KPIs and follows traces of the full WordPress execution. It has the ability to enrich these events, metrics and traces with many details regarding their triggering, before storing them in WordPress database or passing them to external services.\u003C\u002Fp>\n\u003Cp>If you don’t want to use external services, \u003Cstrong>DecaLog\u003C\u002Fstrong> provides the tools to leverage all the benefits of observability right in the WordPress admin dashboard. It supports multisite logs delegation and contains many features to help to protect personal information (user pseudonymization, IP obfuscation, etc.).\u003C\u002Fp>\n\u003Cp>For a full list of supported – internal or third-party – services please, jump to the official \u003Ca href=\"https:\u002F\u002Fperfops.one\u002Fdecalog#services\" rel=\"nofollow ugc\">supported services list\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>DecaLog\u003C\u002Fstrong> can be used in dev\u002Fdebug phases or on production sites: it has nearly no resource impact on the server. It provides an extensive set of WP-CLI commands to help operations too.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>DecaLog\u003C\u002Fstrong> is part of \u003Ca href=\"https:\u002F\u002Fperfops.one\u002F\" rel=\"nofollow ugc\">PerfOps One\u003C\u002Fa>, a suite of free and open source WordPress plugins dedicated to observability and operations performance.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>Developers\u003C\u002Fh4>\n\u003Cp>If you’re a plugins \u002F themes developer and want to take advantage of the logging features of DecaLog, there’s a \u003Ca href=\"https:\u002F\u002Fdecalog.io\u002F\" rel=\"nofollow ugc\">DecaLog SDK\u003C\u002Fa> for you.\u003C\u002Fp>\n\u003Ch4>Support\u003C\u002Fh4>\n\u003Cp>This plugin is free and provided without warranty of any kind. Use it at your own risk, I’m not responsible for any improper use of this plugin, nor for any damage it might cause to your site. Always backup all your data before installing a new plugin.\u003C\u002Fp>\n\u003Cp>Anyway, I’ll be glad to help you if you encounter issues when using this plugin. Just use the support section of this plugin page.\u003C\u002Fp>\n\u003Ch4>Privacy\u003C\u002Fh4>\n\u003Cp>This plugin, as any piece of software, is neither compliant nor non-compliant with privacy laws and regulations. It is your responsibility to use it – by activating the corresponding options or services – with respect for the personal data of your users and applicable laws.\u003C\u002Fp>\n\u003Cp>This plugin doesn’t set any cookie in the user’s browser.\u003C\u002Fp>\n\u003Cp>This plugin may handle personally identifiable information (PII). If the GDPR or CCPA or similar regulation applies to your case, you must use the anonymization options embedded in the plugin and\u002For adapt your processes (consent management, security measure, treatment register, etc.).\u003C\u002Fp>\n\u003Ch4>Donation\u003C\u002Fh4>\n\u003Cp>If you like this plugin or find it useful and want to thank me for the work done, please consider making a donation to \u003Ca href=\"https:\u002F\u002Fwww.laquadrature.net\u002Fen\" rel=\"nofollow ugc\">La Quadrature Du Net\u003C\u002Fa> or the \u003Ca href=\"https:\u002F\u002Fwww.eff.org\u002F\" rel=\"nofollow ugc\">Electronic Frontier Foundation\u003C\u002Fa> which are advocacy groups defending the rights and freedoms of citizens on the Internet. By supporting them, you help the daily actions they perform to defend our fundamental freedoms!\u003C\u002Fp>\n","Capture and log events, metrics and traces on your site. Make WordPress observable - finally!",1000,48272,96,8,"2025-11-27T13:01:00.000Z","6.2","8.1",[22,115,24,116,117],"logging","monitoring","tracing","https:\u002F\u002Fperfops.one\u002Fdecalog","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdecalog.4.5.0.zip",98,"2024-03-26 00:00:00",{"slug":123,"name":124,"version":125,"author":126,"author_profile":127,"description":128,"short_description":129,"active_installs":13,"downloaded":130,"rating":13,"num_ratings":131,"last_updated":132,"tested_up_to":48,"requires_at_least":133,"requires_php":134,"tags":135,"homepage":139,"download_link":140,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"dev-debug-tools","Developer Debug Tools","3.0.1.3","PluginRx","https:\u002F\u002Fprofiles.wordpress.org\u002Fapos37\u002F","\u003Cp>The “Developer Debug Tools” WordPress plugin is a powerhouse for developers and site administrators! It’s a FREE comprehensive toolkit that helps you identify, troubleshoot, and resolve issues in your WordPress site, making debugging a breeze. No premium version available.\u003C\u002Fp>\n\u003Cp>This plugin offers a suite of features to aid in debugging, including, but not limited to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Dashboard with \u003Cstrong>important site information and server metrics\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enhanced log viewer\u003C\u002Fstrong> for \u003Ccode>debug.log\u003C\u002Fcode>, error logs, custom logs, and an activity log\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Config file\u003C\u002Fstrong> viewers and editors for \u003Ccode>wp-config.php\u003C\u002Fcode> and \u003Ccode>.htaccess\u003C\u002Fcode> files\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Meta Data\u003C\u002Fstrong> viewer and editor for users, posts, tax terms, comments, and media\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Database Table records\u003C\u002Fstrong> viewer\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Site Options\u003C\u002Fstrong> viewer and editor\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Globals\u003C\u002Fstrong> viewer\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Defined Constants\u003C\u002Fstrong> viewer\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Transients, Cookies, and Sessions\u003C\u002Fstrong> management\u003C\u002Fli>\n\u003Cli>\u003Cstrong>REST API\u003C\u002Fstrong> viewer and status checker\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Post Types and Taxonomies\u003C\u002Fstrong> viewers\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Auto-Draft\u003C\u002Fstrong> viewer and clearer\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Shortcode Finder\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Cron Jobs\u003C\u002Fstrong> viewer\u003C\u002Fli>\n\u003Cli>\u003Cstrong>PHP Info\u003C\u002Fstrong> and \u003Cstrong>php.ini\u003C\u002Fstrong> viewers\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Discord Notifications\u003C\u002Fstrong> of fatal errors and when users with certain roles log in\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Discord Messenger\u003C\u002Fstrong> for testing connections with Discord\u003C\u002Fli>\n\u003Cli>\u003Cstrong>See who’s online\u003C\u002Fstrong> and \u003Cstrong>last online\u003C\u002Fstrong> dates\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Heartbeat Monitor\u003C\u002Fstrong> for testing WP Heartbeat API sitewide\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Plugins Page Enhancements\u003C\u002Fstrong> with addt plugin data and notes feature\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Security Options\u003C\u002Fstrong> for hiding the plugin and password protection to any admin page\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Admin Bar Tools\u003C\u002Fstrong> such as seeing Post ID\u002Ftype\u002Fstatus, User ID, an interactive centering tool, and more\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Quick Debug Links\u003C\u002Fstrong> for debugging users, posts, and comments\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Gravity Forms\u003C\u002Fstrong> integrations\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>With “Developer Debug Tools”, you can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Identify and fix errors, bugs, and conflicts\u003C\u002Fli>\n\u003Cli>Troubleshoot complex issues with ease\u003C\u002Fli>\n\u003Cli>Update user and post meta straight from the admin area\u003C\u002Fli>\n\u003Cli>Streamline your development and testing workflow\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This plugin is a must-have for any WordPress developer or site administrator who wants to ensure a stable, efficient, and high-performing website. It’s like having a trusty sidekick that helps you tackle even the most challenging debugging tasks!\u003C\u002Fp>\n\u003Ch3>Demo\u003C\u002Fh3>\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\u002F36aebqdzHQw?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","Lots of debugging and testing tools for developers.",13659,4,"2026-02-23T14:54:00.000Z","5.9","8.0",[136,21,137,24,138],"config","developer","testing","https:\u002F\u002Fpluginrx.com\u002Fplugin\u002Fdev-debug-tools\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdev-debug-tools.3.0.1.3.zip",{"attackSurface":142,"codeSignals":202,"taintFlows":231,"riskAssessment":278,"analyzedAt":286},{"hooks":143,"ajaxHandlers":185,"restRoutes":192,"shortcodes":200,"cronEvents":201,"entryPointCount":14,"unprotectedCount":27},[144,150,154,158,163,168,172,174,179,182],{"type":145,"name":146,"callback":147,"file":148,"line":149},"action","rest_api_init","register_rest_routes","App\\Controllers\\LogController.php",26,{"type":145,"name":151,"callback":152,"file":148,"line":153},"admin_enqueue_scripts","enqueue_styles",27,{"type":145,"name":155,"callback":156,"file":148,"line":157},"wp_dashboard_setup","add_dashboard_widget",29,{"type":145,"name":159,"callback":160,"file":161,"line":162},"admin_menu","addMenuPage","App\\Controllers\\MenuController.php",15,{"type":145,"name":164,"callback":165,"file":166,"line":167},"admin_init","registerSettings","App\\Controllers\\SettingsController.php",24,{"type":145,"name":169,"callback":170,"file":166,"line":171},"admin_notices","adminNotice",25,{"type":145,"name":164,"callback":173,"file":166,"line":149},"saveSettings",{"type":145,"name":175,"callback":176,"file":177,"line":178},"plugins_loaded","load_textdomain","simple-log-viewer.php",41,{"type":145,"name":151,"callback":180,"file":177,"line":181},"enqueue_scripts",42,{"type":145,"name":155,"callback":183,"file":177,"line":184},"closure",69,[186],{"action":187,"nopriv":188,"callback":189,"hasNonce":190,"hasCapCheck":188,"file":148,"line":191},"slvpl_manual_log_check",false,"manual_log_check",true,28,[193],{"namespace":194,"route":195,"methods":196,"callback":198,"permissionCallback":199,"file":148,"line":181},"simplelogviewer\u002Fv1","\u002Ferrors",[197],"GET","get_latest_errors","check_logged_in_and_admin_user",[],[],{"dangerousFunctions":203,"sqlUsage":204,"outputEscaping":206,"fileOperations":229,"externalRequests":27,"nonceChecks":14,"capabilityChecks":14,"bundledLibraries":230},[],{"prepared":27,"raw":27,"locations":205},[],{"escaped":207,"rawEcho":11,"locations":208},14,[209,212,213,215,217,219,221,224,226,227],{"file":166,"line":210,"context":211},38,"raw output",{"file":166,"line":181,"context":211},{"file":166,"line":214,"context":211},46,{"file":166,"line":216,"context":211},51,{"file":166,"line":218,"context":211},55,{"file":166,"line":220,"context":211},57,{"file":222,"line":223,"context":211},"App\\Views\\LogView.php",16,{"file":222,"line":225,"context":211},23,{"file":222,"line":157,"context":211},{"file":222,"line":228,"context":211},44,9,[],[232,249,262,270],{"entryPoint":233,"graph":234,"unsanitizedCount":33,"severity":248},"display_dashboard_widget (App\\Views\\LogView.php:14)",{"nodes":235,"edges":246},[236,241],{"id":237,"type":238,"label":239,"file":222,"line":240},"n0","source","$_POST",19,{"id":242,"type":243,"label":244,"file":222,"line":157,"wp_function":245},"n1","sink","echo() [XSS]","echo",[247],{"from":237,"to":242,"sanitized":188},"medium",{"entryPoint":250,"graph":251,"unsanitizedCount":27,"severity":261},"saveSettings (App\\Controllers\\SettingsController.php:61)",{"nodes":252,"edges":259},[253,255],{"id":237,"type":238,"label":239,"file":166,"line":254},63,{"id":242,"type":243,"label":256,"file":166,"line":257,"wp_function":258},"update_option() [Settings Manipulation]",64,"update_option",[260],{"from":237,"to":242,"sanitized":190},"low",{"entryPoint":263,"graph":264,"unsanitizedCount":27,"severity":261},"\u003CSettingsController> (App\\Controllers\\SettingsController.php:0)",{"nodes":265,"edges":268},[266,267],{"id":237,"type":238,"label":239,"file":166,"line":254},{"id":242,"type":243,"label":256,"file":166,"line":257,"wp_function":258},[269],{"from":237,"to":242,"sanitized":190},{"entryPoint":271,"graph":272,"unsanitizedCount":33,"severity":261},"\u003CLogView> (App\\Views\\LogView.php:0)",{"nodes":273,"edges":276},[274,275],{"id":237,"type":238,"label":239,"file":222,"line":240},{"id":242,"type":243,"label":244,"file":222,"line":157,"wp_function":245},[277],{"from":237,"to":242,"sanitized":188},{"summary":279,"deductions":280},"The 'simple-log-viewer' plugin version 1.0.4 exhibits a generally strong security posture with no known historical vulnerabilities.  The static analysis reveals a minimal attack surface, consisting of only two entry points, both of which are protected by authentication checks.  Furthermore, the plugin avoids dangerous functions and exclusively uses prepared statements for its SQL queries, which are positive indicators of secure coding practices.\n\nHowever, there are areas for improvement. The taint analysis identified two flows with unsanitized paths, which, while not resulting in critical or high severity issues in this analysis, represent a potential risk if they were to be exploited in conjunction with other weaknesses. Additionally, only 58% of output escaping is properly implemented, meaning that a significant portion of the plugin's output is not sanitized, potentially leading to cross-site scripting (XSS) vulnerabilities. The presence of file operations (9 total) without specific context in the analysis also warrants attention, as improper handling of file operations can lead to various security issues.\n\nIn conclusion, the plugin is well-protected against common threats like SQL injection and unauthorized access due to its robust handling of authentication and SQL queries. The absence of known CVEs is a significant strength. However, the identified unsanitized paths in taint analysis and the moderate rate of proper output escaping are weaknesses that could be exploited. Addressing these areas would further enhance the plugin's overall security.",[281,283],{"reason":282,"points":162},"Unsanitized paths found in taint analysis",{"reason":284,"points":285},"Moderate output escaping (58% proper)",6,"2026-03-17T00:12:00.859Z",{"wat":288,"direct":295},{"assetPaths":289,"generatorPatterns":291,"scriptPaths":292,"versionParams":293},[290],"\u002Fwp-content\u002Fplugins\u002Fsimple-log-viewer\u002Fpublic\u002Fassets\u002Fjs\u002Findex.js",[],[290],[294],"simple-log-viewer\u002Fpublic\u002Fassets\u002Fjs\u002Findex.js?ver=",{"cssClasses":296,"htmlComments":298,"htmlAttributes":299,"restEndpoints":300,"jsGlobals":302,"shortcodeOutput":304},[297],"slv-log-viewer",[],[],[301],"\u002Fwp-json\u002Fsimplelogviewer\u002Fv1\u002Ferrors",[303],"ajax_object",[]]