[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$flA3aqKCm5ktlczOl459DcxTD4i9VvxwIezb093nP5iM":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":20,"download_link":21,"security_score":22,"vuln_count":11,"unpatched_count":11,"last_vuln_date":23,"fetched_at":24,"vulnerabilities":25,"developer":26,"crawl_stats":23,"alternatives":32,"analysis":33,"fingerprints":109},"support-monitor","Support Monitor – WordPress Support Monitor Plugin","1.0.3","Emtiaz Zahid","https:\u002F\u002Fprofiles.wordpress.org\u002Femtiazzahid\u002F","\u003Cp>Support Monitor will help you find users support topics that are unresolved based on time limit, Monitor specific plugin or multiple at a time\u003C\u002Fp>\n\u003Ch4>Links\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Femtiazzahid\u002Fwp-support-monitor\" rel=\"nofollow ugc\">Github project page\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","A Simple Support Monitoring Tool for WordPress.",0,1231,"","5.9.13","4.0","5.4",[4,18,19],"unresolved-issues","wordpress-support-monitor","https:\u002F\u002Fgithub.com\u002Femtiazzahid\u002Fwp-support-monitor","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsupport-monitor.1.0.3.zip",100,null,"2026-03-15T10:48:56.248Z",[],{"slug":27,"display_name":7,"profile_url":8,"plugin_count":28,"total_installs":11,"avg_security_score":22,"avg_patch_time_days":29,"trust_score":30,"computed_at":31},"emtiazzahid",1,30,94,"2026-04-04T14:48:58.597Z",[],{"attackSurface":34,"codeSignals":78,"taintFlows":99,"riskAssessment":100,"analyzedAt":108},{"hooks":35,"ajaxHandlers":70,"restRoutes":71,"shortcodes":72,"cronEvents":77,"entryPointCount":28,"unprotectedCount":11},[36,41,45,50,55,58,63,67],{"type":37,"name":38,"callback":38,"file":39,"line":40},"action","admin_menu","includes\\Admin.php",10,{"type":37,"name":42,"callback":43,"file":39,"line":44},"admin_enqueue_scripts","enqueue_scripts",38,{"type":37,"name":46,"callback":47,"file":48,"line":49},"rest_api_init","register_routes","includes\\Api.php",19,{"type":37,"name":42,"callback":51,"priority":52,"file":53,"line":54},"register",5,"includes\\Assets.php",12,{"type":37,"name":56,"callback":51,"priority":52,"file":53,"line":57},"wp_enqueue_scripts",14,{"type":37,"name":59,"callback":60,"file":61,"line":62},"plugins_loaded","init_plugin","plugin.php",82,{"type":37,"name":64,"callback":65,"file":61,"line":66},"init","init_classes",205,{"type":37,"name":64,"callback":68,"file":61,"line":69},"localization_setup",208,[],[],[73],{"tag":74,"callback":75,"file":76,"line":40},"vue-app","render_frontend","includes\\Frontend.php",[],{"dangerousFunctions":79,"sqlUsage":80,"outputEscaping":96,"fileOperations":11,"externalRequests":28,"nonceChecks":11,"capabilityChecks":28,"bundledLibraries":98},[],{"prepared":11,"raw":81,"locations":82},4,[83,87,90,93],{"file":84,"line":85,"context":86},"includes\\Api\\Plugins.php",74,"$wpdb->get_results() with variable interpolation",{"file":84,"line":88,"context":89},124,"$wpdb->query() with variable interpolation",{"file":91,"line":92,"context":86},"includes\\Api\\UnresolvedIssues.php",56,{"file":61,"line":94,"context":95},275,"$wpdb->get_var() with variable interpolation",{"escaped":11,"rawEcho":11,"locations":97},[],[],[],{"summary":101,"deductions":102},"The \"support-monitor\" plugin version 1.0.3 demonstrates a generally positive security posture based on the provided static analysis.  The absence of any known vulnerabilities in its history is a strong indicator of good development practices and diligent maintenance.  Furthermore, the plugin effectively utilizes output escaping and capability checks, which are crucial for preventing common web vulnerabilities.  The limited attack surface, consisting of a single shortcode with no unprotected entry points, also contributes to its security. \n\nHowever, there are areas for improvement.  The most significant concern is the use of raw SQL queries without prepared statements.  This practice, seen in 4 out of 4 queries, introduces a substantial risk of SQL injection vulnerabilities, especially if any of the data involved in these queries originates from user input.  The lack of nonce checks on its single entry point, while not directly exploitable without other factors, is a missed opportunity for enhanced security against CSRF attacks.  While no critical taint flows were identified, the raw SQL queries represent a potential pathway for such issues to emerge if not addressed. \n\nIn conclusion, the \"support-monitor\" plugin is built on a solid foundation with no known historical exploits and good practices in output sanitization and authorization.  Its strengths lie in its minimal attack surface and effective use of capability checks. The primary weakness lies in its handling of database interactions, specifically the reliance on un-prepared SQL statements, which presents a tangible risk that should be prioritized for remediation.",[103,106],{"reason":104,"points":105},"Raw SQL queries without prepared statements",15,{"reason":107,"points":52},"Missing nonce checks on entry points","2026-03-17T05:41:48.211Z",{"wat":110,"direct":119},{"assetPaths":111,"generatorPatterns":114,"scriptPaths":115,"versionParams":116},[112,113],"\u002Fwp-content\u002Fplugins\u002Fsupport-monitor\u002Fassets\u002Fcss\u002Fstyle.css","\u002Fwp-content\u002Fplugins\u002Fsupport-monitor\u002Fassets\u002Fjs\u002Fbackend.js",[],[113],[117,118],"support-monitor\u002Fassets\u002Fcss\u002Fstyle.css?ver=","support-monitor\u002Fassets\u002Fjs\u002Fbackend.js?ver=",{"cssClasses":120,"htmlComments":121,"htmlAttributes":122,"restEndpoints":123,"jsGlobals":125,"shortcodeOutput":127},[],[],[],[124],"\u002Fwp-json\u002Fsupportmonitor\u002Fv1\u002Fget-plugins",[126],"SupportMonitor",[]]