[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f7YZo3rXoiCOO8TOV9pUYFYVzc--xIk2V1IXFimiOUZk":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":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":17,"download_link":22,"security_score":23,"vuln_count":13,"unpatched_count":13,"last_vuln_date":24,"fetched_at":25,"vulnerabilities":26,"developer":27,"crawl_stats":24,"alternatives":34,"analysis":35,"fingerprints":101},"seo-keyword-emphasis","SEO Keyword Emphasis","1.0.0","Ovidiu Purdea","https:\u002F\u002Fprofiles.wordpress.org\u002Fpovidiu\u002F","\u003Cp>This plugin help you to emphasis the keywords inside your posts or pages. You have the option to make the keyword blold, italic, underline, change the background color, change the foreground color. You can use multiple keywords.\u003C\u002Fp>\n\u003Cp>Keyword emphasis is a means of highlighting text within a page. Keyword emphasis can be utilised in a number of different ways for a number of different reasons. Typically, website emphasis was a part of the initial HTML coding standards. Even to this day, keyword emphasis and content emphasis remain incredibly popular, moreso for the end user rather than just search engines.\u003Cbr \u002F>\n \u003C\u002Fp>\n","This plugin help you to emphasis the keywords inside your posts or pages. You have the option to make the keyword blold, italic, underline, change the …",10,1704,0,"2013-11-25T08:22:00.000Z","3.7.41","3.0.0","",[19,20,21,4],"keyword-decoration","keyword-emphasis","keywords-highlight","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fseo-keyword-emphasis.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":28,"display_name":7,"profile_url":8,"plugin_count":29,"total_installs":30,"avg_security_score":23,"avg_patch_time_days":31,"trust_score":32,"computed_at":33},"povidiu",4,280,30,84,"2026-04-04T14:21:37.570Z",[],{"attackSurface":36,"codeSignals":60,"taintFlows":88,"riskAssessment":89,"analyzedAt":100},{"hooks":37,"ajaxHandlers":56,"restRoutes":57,"shortcodes":58,"cronEvents":59,"entryPointCount":13,"unprotectedCount":13},[38,43,47,52],{"type":39,"name":40,"callback":41,"file":42,"line":11},"action","admin_menu","text_setting_menu","seo-keyword-empasis.php",{"type":39,"name":44,"callback":45,"file":42,"line":46},"admin_init","highlighted_text_register_settings",11,{"type":48,"name":49,"callback":50,"file":42,"line":51},"filter","the_content","apply_seoke_word_highligher",168,{"type":39,"name":53,"callback":54,"file":42,"line":55},"wp_head","seoke_word_highligher_css",260,[],[],[],[],{"dangerousFunctions":61,"sqlUsage":62,"outputEscaping":64,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":87},[],{"prepared":13,"raw":13,"locations":63},[],{"escaped":13,"rawEcho":11,"locations":65},[66,69,71,73,75,77,79,81,83,85],{"file":42,"line":67,"context":68},77,"raw output",{"file":42,"line":70,"context":68},107,{"file":42,"line":72,"context":68},108,{"file":42,"line":74,"context":68},109,{"file":42,"line":76,"context":68},115,{"file":42,"line":78,"context":68},118,{"file":42,"line":80,"context":68},130,{"file":42,"line":82,"context":68},143,{"file":42,"line":84,"context":68},156,{"file":42,"line":86,"context":68},252,[],[],{"summary":90,"deductions":91},"The 'seo-keyword-emphasis' v1.0.0 plugin exhibits a generally strong security posture based on the provided static analysis. The complete absence of identified dangerous functions, raw SQL queries, file operations, and external HTTP requests is commendable. Furthermore, the lack of any recorded vulnerabilities, critical or otherwise, suggests a history of security awareness or simply a lack of past exploitation.\n\nHowever, a significant concern arises from the complete lack of output escaping. With 10 total outputs and 0% properly escaped, this opens the plugin to potential Cross-Site Scripting (XSS) vulnerabilities. Any dynamic content displayed to users could be manipulated by attackers to inject malicious scripts. Additionally, the absence of nonce and capability checks across all identified entry points (even though there are currently zero) represents a potential future risk if the plugin's functionality expands without proper security hardening.\n\nIn conclusion, while the plugin benefits from a clean vulnerability history and the absence of many common dangerous code patterns, the unescaped output is a critical weakness that needs immediate attention. The lack of any explicit security checks on entry points, while not a current risk due to the zero attack surface, is a warning sign for future development. Addressing the output escaping issue is paramount to mitigating XSS risks.",[92,95,98],{"reason":93,"points":94},"Unescaped output on all outputs",20,{"reason":96,"points":97},"No nonce checks on entry points",5,{"reason":99,"points":97},"No capability checks on entry points","2026-03-17T00:59:03.207Z",{"wat":102,"direct":107},{"assetPaths":103,"generatorPatterns":104,"scriptPaths":105,"versionParams":106},[],[],[],[],{"cssClasses":108,"htmlComments":110,"htmlAttributes":111,"restEndpoints":112,"jsGlobals":113,"shortcodeOutput":114},[109],"wh_highlighted",[],[],[],[],[]]