[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fvUXk5gC6Tnn_1X7oE0o1aNi0G42BP5PRFbgDhD6he00":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":23,"download_link":24,"security_score":25,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":36,"analysis":37,"fingerprints":81},"forbidden-author-words","Forbidden Author Words","2.0.0","Yogesh Pawar","https:\u002F\u002Fprofiles.wordpress.org\u002Fpawaryogesh1989\u002F","\u003Cp>This plugin restricts the Author the use of words which are not allowed to use in Post title or content.\u003Cbr \u002F>\nIf you manage a multi-author blog and want authors to avoid using certain words or phrases, then this plugin would be very useful as it is not easy to keep all authors informed about your editorial style and policy on a multi-author site..\u003C\u002Fp>\n\u003Ch4>Details\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Plugin Option in Admin section to add the words that are to be restricted.\u003C\u002Fli>\n\u003Cli>Option to either restrict words in Post title or Post content or Both.\u003C\u002Fli>\n\u003Cli>Option to display the “Restricted words” as a notice in the entire Admin section. (Can be turned off)\u003C\u002Fli>\n\u003C\u002Ful>\n","Use this plugin to restrict Authors to use of some words that should not used.",10,1543,0,"2021-01-05T11:15:00.000Z","5.6.17","5.0","",[4,19,20,21,22],"post-title-review","restrict-post-content","restrict-post-title","restrict-words-in-post-titles","http:\u002F\u002Fwww.clariontechnologies.co.in","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fforbidden-author-words.zip",85,null,"2026-03-15T14:54:45.397Z",[],{"slug":30,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":32,"avg_security_score":25,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"pawaryogesh1989",11,600,30,84,"2026-04-04T13:47:04.838Z",[],{"attackSurface":38,"codeSignals":62,"taintFlows":71,"riskAssessment":72,"analyzedAt":80},{"hooks":39,"ajaxHandlers":58,"restRoutes":59,"shortcodes":60,"cronEvents":61,"entryPointCount":13,"unprotectedCount":13},[40,46,50,54],{"type":41,"name":42,"callback":43,"file":44,"line":45},"action","admin_menu","wp_forbidden_words_menu","classes\\class.forbidden.words.php",12,{"type":41,"name":47,"callback":48,"file":44,"line":49},"admin_init","wp_forbidden_words_settings",13,{"type":41,"name":51,"callback":52,"priority":11,"file":44,"line":53},"transition_post_status","post_forbidden_author_words",14,{"type":41,"name":55,"callback":56,"file":44,"line":57},"admin_notices","forbidden_words_message",15,[],[],[],[],{"dangerousFunctions":63,"sqlUsage":64,"outputEscaping":66,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":69,"bundledLibraries":70},[],{"prepared":13,"raw":13,"locations":65},[],{"escaped":67,"rawEcho":13,"locations":68},2,[],1,[],[],{"summary":73,"deductions":74},"The 'forbidden-author-words' v2.0.0 plugin exhibits a strong security posture based on the provided static analysis. The absence of any identified attack surface points, dangerous functions, unsanitized taint flows, raw SQL queries, or unescaped output signals diligent development practices. The plugin also has no recorded vulnerability history, which further reinforces its apparent security.  The single capability check indicates that at least some administrative control is likely enforced for any relevant functionality, which is a positive sign. However, the lack of nonce checks on AJAX handlers and the absence of REST API routes are notable omissions. While the current analysis shows zero unprotected entry points, this could change if the plugin were to evolve and introduce new functionalities that utilize these often-exploited mechanisms without proper security. The vulnerability history is clean, but this could also be attributed to a small user base or a lack of targeted analysis rather than inherent invulnerability. Overall, the plugin appears secure for its current functionality, but developers should remain vigilant about implementing proper security measures like nonce checks if the plugin's scope expands.",[75,78],{"reason":76,"points":77},"No nonce checks on AJAX handlers",5,{"reason":79,"points":77},"No REST API routes with permission callbacks","2026-03-16T23:39:04.460Z",{"wat":82,"direct":89},{"assetPaths":83,"generatorPatterns":85,"scriptPaths":86,"versionParams":87},[84],"\u002Fwp-content\u002Fplugins\u002Fforbidden-author-words\u002Fjs\u002Fforbidden-author-words.js",[],[84],[88],"forbidden-author-words\u002Fjs\u002Fforbidden-author-words.js?ver=",{"cssClasses":90,"htmlComments":91,"htmlAttributes":92,"restEndpoints":93,"jsGlobals":94,"shortcodeOutput":95},[],[],[],[],[],[]]