[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fi2MXXxN5eUw9AoY4Gtav6ierlTsphpW6FTqvQEBrDAA":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":24,"download_link":25,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":36,"analysis":130,"fingerprints":192},"wp-pingpreserver","WP_PingPreserver","0.4","scottsm","https:\u002F\u002Fprofiles.wordpress.org\u002Fscottsm\u002F","\u003Cp>For a while, I’ve been a bit annoyed with WordPress losing pings (those automatic links on your blog when someone links to you) anytime someone links to more than one of my posts. It turns out WordPress’s comment flood prevention is getting in the way. This plugin prevents WordPress from discarding these pings.\u003C\u002Fp>\n","Prevents WordPress from eating pings that come too quickly in succession (i.e. a single post linking to more than one of your pages).",10,2283,0,"2008-01-22T02:43:00.000Z","2.3.1","1.5","",[19,20,21,22,23],"comments","fix","hack","ping","trackback","http:\u002F\u002Fscott.sherrillmix.com\u002Fblog\u002Fprogrammer\u002Fweb\u002FWP_PingSaver\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-pingpreserver.0.4.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":32,"avg_security_score":26,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},5,60,30,84,"2026-04-05T02:23:54.374Z",[37,59,77,99,116],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":47,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":53,"homepage":56,"download_link":57,"security_score":58,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"hide-trackbacks","Hide Trackbacks","1.1.7","Sander van Dragt","https:\u002F\u002Fprofiles.wordpress.org\u002Fpacifika\u002F","\u003Cp>Introducing \u003Cem>Hide Trackbacks\u003C\u002Fem> – keep the benefits of track- and pingbacks (know when someone writes about posts) while keeping the comments clean and uncluttered.\u003C\u002Fp>\n\u003Cp>After enabling the plugin, trackbacks and pingbacks are no longer shown on your posts and the comment count is updated correctly to reflect this. They remain accessible via the admin panel.\u003C\u002Fp>\n\u003Cp>Original code created by  \u003Ca href=\"http:\u002F\u002Fwww.honeytechblog.com\u002Fhow-to-remove-tracbacks-and-pings-from-wordpress-posts\u002F\" rel=\"nofollow ugc\">Honey Singh\u003C\u002Fa> (used with permission of the author).\u003C\u002Fp>\n","Prevents trackbacks and pingbacks from showing up as comments on posts.",400,17591,94,6,"2025-12-07T10:00:00.000Z","6.9.4","5.8","7.0",[19,54,55,23],"pingback","spam","http:\u002F\u002Fwp.me\u002Fp1vXha-4u","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhide-trackbacks.1.1.7.zip",100,{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":13,"num_ratings":13,"last_updated":69,"tested_up_to":50,"requires_at_least":70,"requires_php":52,"tags":71,"homepage":75,"download_link":76,"security_score":58,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"really-simple-disable-comments","Really Simple Disable Comments","0.2.1","NEXTFLY® Web Design","https:\u002F\u002Fprofiles.wordpress.org\u002Fnextfly\u002F","\u003Cp>Really Simple Disable Comments is a lightweight plugin that completely disables WordPress comments functionality with a single activation. No configuration needed!\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Disables comments on all post types\u003C\u002Fli>\n\u003Cli>Removes comment-related UI elements\u003C\u002Fli>\n\u003Cli>Disables trackbacks and pingbacks\u003C\u002Fli>\n\u003Cli>Removes comment-related admin menu items and dashboard widgets\u003C\u002Fli>\n\u003Cli>Hides comment counts from dashboard “At a Glance” widget\u003C\u002Fli>\n\u003Cli>Hides “Recent Comments” section from dashboard Activity widget\u003C\u002Fli>\n\u003Cli>Disables all comment-related Gutenberg blocks\u003C\u002Fli>\n\u003Cli>Clean and efficient code with no settings required\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>What Gets Disabled?\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Comment forms and displays\u003C\u002Fli>\n\u003Cli>Admin menu items and dashboard widgets\u003C\u002Fli>\n\u003Cli>Comment-related Gutenberg blocks\u003C\u002Fli>\n\u003Cli>Trackbacks and pingbacks\u003C\u002Fli>\n\u003Cli>Comment-related UI elements in themes\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Developer Friendly\u003C\u002Fh4>\n\u003Cp>The plugin includes various filters and actions for developers to customize its behavior:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>rsdc_post_type\u003C\u002Fcode> – Filter the post type before removing comment support\u003C\u002Fli>\n\u003Cli>\u003Ccode>rsdc_comments_status\u003C\u002Fcode> – Filter the comments status\u003C\u002Fli>\n\u003Cli>\u003Ccode>rsdc_hide_existing_comments\u003C\u002Fcode> – Filter the hidden comments array\u003C\u002Fli>\n\u003Cli>\u003Ccode>rsdc_hide_ui_styles\u003C\u002Fcode> – Filter the CSS used to hide comment UI elements\u003C\u002Fli>\n\u003Cli>\u003Ccode>rsdc_block_editor_settings\u003C\u002Fcode> – Filter the block editor settings\u003C\u002Fli>\n\u003Cli>\u003Ccode>rsdc_allowed_blocks\u003C\u002Fcode> – Filter the allowed Gutenberg blocks\u003C\u002Fli>\n\u003C\u002Ful>\n","Effortlessly disable all comments and trackback functionality across your entire WordPress site by activating this plugin.",200,2437,"2025-12-09T15:20:00.000Z","5.0",[19,72,73,74],"disable-comments","disable-pingbacks","disable-trackbacks","https:\u002F\u002Fgithub.com\u002Fnextfly\u002Freally-simple-disable-comments","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Freally-simple-disable-comments.0.2.1.zip",{"slug":78,"name":79,"version":80,"author":81,"author_profile":82,"description":83,"short_description":84,"active_installs":58,"downloaded":85,"rating":86,"num_ratings":87,"last_updated":88,"tested_up_to":89,"requires_at_least":90,"requires_php":17,"tags":91,"homepage":94,"download_link":95,"security_score":96,"vuln_count":97,"unpatched_count":97,"last_vuln_date":98,"fetched_at":28},"manuall-dofollow","SMu Manual DoFollow","1.8.1","Stefan M.","https:\u002F\u002Fprofiles.wordpress.org\u002Fstefan-m-1\u002F","\u003Cp>This plugin will set all Trackbacks and Pingbacks automatically to DoFollow Links.\u003C\u002Fp>\n\u003Cp>The user comments will get after \u003Ccode>X\u003C\u002Fcode> comments from a unique mailaddress automatically DoFollow status. All other comments have NoFollow, except the Admin enable manually the DoFollow Status. The status which is set manual (if DoFollow or NoFollow) will overrides the automatical process. So, you have the control if someone gets sooner the DoFollow status, or never maybe. Of corse, the automatism can be disabled to do the hole work manually.\u003C\u002Fp>\n\u003Cp>You get an support automatism, that you don’t need to check daily, but have the full control power.\u003C\u002Fp>\n\u003Cp>Additonal this plugin validated all DoFollow URLs and will notice if there are broken links. Broken Links are very bad the Rank in the Search Engines (SEO).\u003C\u002Fp>\n\u003Cp>Home Page of the Plugin: \u003Ca href=\"http:\u002F\u002Fblog.murawski.ch\u002F2010\u002F09\u002Fwordpress-manual-dofollow-plugin\u002F\" title=\"IT Blögg - WordPress Manual DoFollow Plugin\" rel=\"nofollow ugc\">IT Blögg – WordPress Manual DoFollow Plugin\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>If you have a wish for new functions, please contact me.\u003C\u002Fp>\n","SMu DoFollow has many DoFollow Options (Manual or Automatism) and included URL Validator (Manual, WP-Cron or Cronjob).",10570,86,3,"2015-12-21T09:46:00.000Z","4.1.42","3.0.0",[19,92,93,54,23],"dofollow","nofollow","http:\u002F\u002Fblog.murawski.ch\u002F2010\u002F09\u002Fwordpress-manual-dofollow-plugin\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmanuall-dofollow.zip",63,1,"2025-07-07 00:00:00",{"slug":100,"name":101,"version":102,"author":103,"author_profile":104,"description":105,"short_description":106,"active_installs":58,"downloaded":107,"rating":13,"num_ratings":13,"last_updated":108,"tested_up_to":109,"requires_at_least":110,"requires_php":17,"tags":111,"homepage":114,"download_link":115,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"pingback-killer","Pingback Killer","1.0","chrisguitarguy","https:\u002F\u002Fprofiles.wordpress.org\u002Fchrisguitarguy\u002F","\u003Cp>Hate Pingbacks and Trackbacks?  Me too.  Pingback Killer disables of of WordPress’ built in pingback functionality.\u003C\u002Fp>\n\u003Cp>This is a very simple plugin that…\u003Cbr \u002F>\n1. Removes the \u003Ccode>X-Pingback\u003C\u002Fcode> header WordPress sends\u003Cbr \u002F>\n2. Causes any \u003Ccode>bloginfo('ping_backurl')\u003C\u002Fcode> call to return an empty string\u003Cbr \u002F>\n3. Hijacks the two options relating to pingbacks\u003Cbr \u002F>\n4. Removes the \u002Ftrackback\u002F rewrite rules\u003C\u002Fp>\n\u003Cp>There are no options pages, it just works.\u003C\u002Fp>\n\u003Cp>Bugs?  Problems?  \u003Ca href=\"http:\u002F\u002Fpmg.co\u002Fcontact\" rel=\"nofollow ugc\">Get in touch\u003C\u002Fa>.\u003C\u002Fp>\n","Pingback Killer disables all of WordPress' pingback functionality.",6345,"2011-10-28T21:10:00.000Z","3.3.2","3.2",[19,112,113],"pingbacks","trackbacks","http:\u002F\u002Fpmg.co\u002Fpingback-killer","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpingback-killer.1.0.zip",{"slug":117,"name":118,"version":102,"author":119,"author_profile":120,"description":121,"short_description":122,"active_installs":58,"downloaded":123,"rating":58,"num_ratings":87,"last_updated":124,"tested_up_to":125,"requires_at_least":109,"requires_php":17,"tags":126,"homepage":128,"download_link":129,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"remove-pingback-trackback-comments","Remove Pingback-Trackback Comments","Pau Iglesias","https:\u002F\u002Fprofiles.wordpress.org\u002Fpauiglesias\u002F","\u003Cp>When your blog posts receive pingbacks and trackbacks usually they are displayed together with user opinions.\u003C\u002Fp>\n\u003Cp>But if you don’t like to see this additional data, or you think pingbacks and trackbacks are not valuable for your blog, here is a tool to remove them.\u003C\u002Fp>\n\u003Cp>This plugin allows you to delete all pingbacks and trackbacks comments from your blog, leaving only user comments.\u003C\u002Fp>\n\u003Cp>Furthermore turns to closed the ping status of existing posts still allowing new notifications, avoiding them future pingbacks or trackbacks.\u003C\u002Fp>\n\u003Cp>And for new posts, to avoid more notifications, updates the default post ping status value to closed (this option is available in Discussion Settings section).\u003C\u002Fp>\n\u003Cp>Full support for any kind of custom post types. There is a filter for developers if you want to exclude a particular post type.\u003C\u002Fp>\n\u003Cp>This plugin provides a single one step form to do these changes, but previously it’s strongelly recommended you perform a database backup.\u003C\u002Fp>\n\u003Cp>Once completed this process, you will not receive more pingbacks or trackbacks unless you do not change posts or blog notifications configuration.\u003C\u002Fp>\n","One step process to remove pingbacks and trackbacks and leave only real user opinions in your posts comments.",4651,"2015-08-31T11:02:00.000Z","4.3.34",[127,19,54,112,23],"comment","http:\u002F\u002Fblogestudio.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fremove-pingback-trackback-comments.1.0.zip",{"attackSurface":131,"codeSignals":143,"taintFlows":153,"riskAssessment":179,"analyzedAt":191},{"hooks":132,"ajaxHandlers":139,"restRoutes":140,"shortcodes":141,"cronEvents":142,"entryPointCount":13,"unprotectedCount":13},[133],{"type":134,"name":135,"callback":136,"priority":11,"file":137,"line":138},"filter","comment_flood_filter","pingpreserver_comment_flood_fixer","wp_pingpreserver.php",12,[],[],[],[],{"dangerousFunctions":144,"sqlUsage":145,"outputEscaping":150,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":152},[],{"prepared":13,"raw":97,"locations":146},[147],{"file":137,"line":148,"context":149},21,"$wpdb->get_var() with variable interpolation",{"escaped":13,"rawEcho":13,"locations":151},[],[],[154,171],{"entryPoint":155,"graph":156,"unsanitizedCount":97,"severity":170},"pingpreserver_comment_flood_fixer (wp_pingpreserver.php:15)",{"nodes":157,"edges":167},[158,162],{"id":159,"type":160,"label":161,"file":137,"line":148},"n0","source","$_SERVER['REMOTE_ADDR']",{"id":163,"type":164,"label":165,"file":137,"line":148,"wp_function":166},"n1","sink","get_var() [SQLi]","get_var",[168],{"from":159,"to":163,"sanitized":169},false,"high",{"entryPoint":172,"graph":173,"unsanitizedCount":97,"severity":170},"\u003Cwp_pingpreserver> (wp_pingpreserver.php:0)",{"nodes":174,"edges":177},[175,176],{"id":159,"type":160,"label":161,"file":137,"line":148},{"id":163,"type":164,"label":165,"file":137,"line":148,"wp_function":166},[178],{"from":159,"to":163,"sanitized":169},{"summary":180,"deductions":181},"The wp-pingpreserver v0.4 plugin exhibits a mixed security posture. On the positive side, there are no registered CVEs, no bundled libraries, no file operations, no external HTTP requests, and all detected outputs are properly escaped. This suggests a good level of attention to common web application security pitfalls. However, the static analysis reveals significant concerns. The presence of a raw SQL query without prepared statements is a notable risk that could lead to SQL injection vulnerabilities if the query is not properly sanitized before execution. Furthermore, the taint analysis indicates two flows with unsanitized paths, classified as high severity. These flows represent potential avenues for attackers to inject malicious code or data into the application if the input is not rigorously validated and neutralized. The complete absence of nonce and capability checks on any entry points is also a critical oversight, leaving the plugin vulnerable to cross-site request forgery (CSRF) and unauthorized privilege escalation attacks if any logic relies on user actions.",[182,184,187,189],{"reason":183,"points":138},"High severity unsanitized taint flows",{"reason":185,"points":186},"Raw SQL query without prepared statements",8,{"reason":188,"points":11},"Missing capability checks on entry points",{"reason":190,"points":11},"Missing nonce checks on entry points","2026-03-17T00:38:11.136Z",{"wat":193,"direct":198},{"assetPaths":194,"generatorPatterns":195,"scriptPaths":196,"versionParams":197},[],[],[],[],{"cssClasses":199,"htmlComments":200,"htmlAttributes":201,"restEndpoints":202,"jsGlobals":203,"shortcodeOutput":204},[],[],[],[],[],[]]