[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$foafxfSZbTYBJSm2dAwHmPtIf_U7nebviBv73jalEYuc":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":18,"download_link":22,"security_score":23,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":26,"vulnerabilities":27,"developer":28,"crawl_stats":25,"alternatives":36,"analysis":135,"fingerprints":307},"push-syndication","Push Syndication","1.0","Automattic","https:\u002F\u002Fprofiles.wordpress.org\u002Fautomattic\u002F","\u003Cp>Syndication helps users manage posts across multiple sites. It’s useful when managing posts on different platforms. With a single click you can push a post to more than 100 sites.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fvip.wordpress.com\u002Fplugins\u002Fsyndication\u002F\" rel=\"nofollow ugc\">Full documentation here.\u003C\u002Fa>\u003C\u002Fp>\n","Syndication helps users manage posts across multiple sites. It's useful when managing posts on different platforms. With a single click you can p &hellip;",90,9826,86,4,"2018-12-14T06:48:00.000Z","5.0.25","3.4","",[20,21],"wordpress-com-rest","xmlrpc","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpush-syndication.1.0.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":29,"display_name":7,"profile_url":8,"plugin_count":30,"total_installs":31,"avg_security_score":32,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"automattic",213,19158100,92,1384,73,"2026-04-03T23:29:55.589Z",[37,55,75,97,118],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":13,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":18,"tags":51,"homepage":52,"download_link":53,"security_score":54,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":26},"disable-xml-rpc","Disable XML-RPC","1.0.1","Phil Erb","https:\u002F\u002Fprofiles.wordpress.org\u002Fphilerb\u002F","\u003Cp>Pretty simply, this plugin uses the built-in WordPress filter “xmlrpc_enabled” to disable the XML-RPC API on a WordPress site running 3.5 or above.\u003C\u002Fp>\n\u003Cp>Beginning in 3.5, XML-RPC is enabled by default. Additionally, the option to disable\u002Fenable XML-RPC was removed. For various reasons, site owners may wish to disable this functionality. This plugin provides an easy way to do so.\u003C\u002Fp>\n","Disables the XML-RPC API in WordPress 3.5+, which is enabled by default.",200000,604200,29,"2025-12-03T01:28:00.000Z","6.9.4","3.5",[21],"http:\u002F\u002Fwww.philerb.com\u002Fwp-plugins\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-xml-rpc.1.0.1.zip",100,{"slug":56,"name":57,"version":58,"author":59,"author_profile":60,"description":61,"short_description":62,"active_installs":63,"downloaded":64,"rating":65,"num_ratings":66,"last_updated":67,"tested_up_to":49,"requires_at_least":68,"requires_php":18,"tags":69,"homepage":73,"download_link":74,"security_score":54,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":26},"disable-xml-rpc-api","Disable XML-RPC-API","2.1.7","Amin Nazemi","https:\u002F\u002Fprofiles.wordpress.org\u002Faminnz\u002F","\u003Cp>Protect your website from xmlrpc brute-force attacks,DOS and DDOS attacks, this plugin disables the XML-RPC and trackbacks-pingbacks on your WordPress website.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>PLUGIN FEATURES\u003C\u002Fstrong>\u003Cbr \u002F>\n(These are options you can enable or disable each one)\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Disable access to xmlrpc.php file using .httacess file \u003C\u002Fli>\n\u003Cli>Automatically change htaccess file permission to read-only (0444)\u003C\u002Fli>\n\u003Cli>Disable X-pingback to minimize CPU usage \u003C\u002Fli>\n\u003Cli>Disable selected methods from XML-RPC\u003C\u002Fli>\n\u003Cli>Remove pingback-ping link from header\u003C\u002Fli>\n\u003Cli>Disable trackbacks and pingbacks to avoid spammers and hackers\u003C\u002Fli>\n\u003Cli>Rename XML-RPC slug to whatever you want\u003C\u002Fli>\n\u003Cli>Black list IPs for XML-RPC\u003C\u002Fli>\n\u003Cli>White list IPs for XML-RPC\u003C\u002Fli>\n\u003Cli>Some options to speed-up your wordpress website\u003C\u002Fli>\n\u003Cli>Disable JSON REST API\u003C\u002Fli>\n\u003Cli>Hide WordPress Version\u003C\u002Fli>\n\u003Cli>Disable built-in WordPress file editor\u003C\u002Fli>\n\u003Cli>Disable wlw manifest\u003C\u002Fli>\n\u003Cli>And some other options\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>What is XMLRPC\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>XML-RPC, or XML Remote Procedure Call is a protocol which uses XML to encode its calls and HTTP as a transport mechanism.\u003Cbr \u002F>\nBeginning in WordPress 3.5, XML-RPC is enabled by default. Additionally, the option to disable\u002Fenable XML-RPC was removed. For various reasons, site owners may wish to disable this functionality. This plugin provides an easy way to do so.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Why you should disable XML-RPC\u003C\u002Fstrong>\u003Cbr \u002F>\n\u003Cem>Xmlrpc has two main weaknesses\u003C\u002Fem>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Brute force attacks:\u003Cbr \u002F>\nAttackers try to login to WordPress using xmlrpc.php with as many username\u002Fpassword combinations as they can enter. A method within xmlrpc.php allows the attacker to use a single command (system.multicall) to guess hundreds of passwords. Daniel Cid at Sucuri described it well in October 2015: “With only 3 or 4 HTTP requests, the attackers could try thousands of passwords, bypassing security tools that are designed to look and block brute force attempts.”\u003C\u002Fli>\n\u003Cli>Denial of Service Attacks via Pingback:\u003Cbr \u002F>\nBack in 2013, attackers sent Pingback requests through xmlrpc.php of approximately 2500 WordPress sites to “herd (these sites) into a voluntary botnet,” according to Gur Schatz at Incapsula. “This gives any attacker a virtually limitless set of IP addresses to Distribute a Denial of Service attack across a network of over 100 million WordPress sites, without having to compromise them.”\u003C\u002Fli>\n\u003C\u002Ful>\n","A simple and lightweight plugin to disable XML-RPC API, X-Pingback and pingback-ping in WordPress 3.5+ for a faster and more secure website",100000,792973,82,42,"2026-02-04T06:54:00.000Z","5.0",[38,70,71,72,21],"disable-xmlrpc","pingback","stop-brute-force-attacks","https:\u002F\u002Fneatma.com\u002Fdsxmlrpc-plugin\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-xml-rpc-api.zip",{"slug":76,"name":77,"version":78,"author":79,"author_profile":80,"description":81,"short_description":82,"active_installs":83,"downloaded":84,"rating":85,"num_ratings":86,"last_updated":87,"tested_up_to":88,"requires_at_least":89,"requires_php":90,"tags":91,"homepage":95,"download_link":96,"security_score":23,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":26},"remove-xmlrpc-pingback-ping","Remove & Disable XML-RPC Pingback","1.6","cleverplugins","https:\u002F\u002Fprofiles.wordpress.org\u002Fcleverplugins\u002F","\u003Cp>Prevent your WordPress site from participating and being a victim of pingback denial of service attacks. \u003Cstrong>After activation the plugin automatically disables XML-RPC. There’s no need to configure anything.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>By disabling the XML-RPC pingback you’ll:\u003Cbr \u002F>\n* lower your server CPU usage\u003Cbr \u002F>\n* prevent malicious scripts from using your site to run pingback denial of service attacks\u003Cbr \u002F>\n* prevent malicious scripts to run denial of service attacks on your site via pingback\u003C\u002Fp>\n\u003Cp>From sucuri.net:\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>Any WordPress site with Pingback enabled (which is on by default) can be used in DDOS attacks against other sites.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>Learn More\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fwptavern.com\u002Fhow-to-prevent-wordpress-from-participating-in-pingback-denial-of-service-attacks\" rel=\"nofollow ugc\">How To Prevent WordPress From Participating In Pingback Denial of Service Attacks\u003C\u002Fa> – wptavern.com\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fblog.sucuri.net\u002F2014\u002F03\u002Fmore-than-162000-wordpress-sites-used-for-distributed-denial-of-service-attack.html\" rel=\"nofollow ugc\">More Than 162,000 WordPress Sites Used for Distributed Denial of Service Attack\u003C\u002Fa> – sucuri.net\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fhackguard.com\u002Fxmlrpc-php-ping-backs-hackers-denial-service-attacks\" rel=\"nofollow ugc\">xmlrpc.php and Pingbacks and Denial of Service Attacks, Oh My!\u003C\u002Fa> – hackguard.com\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Is Your Site Attacking Others?\u003C\u002Fh4>\n\u003Cp>Use \u003Ca href=\"http:\u002F\u002Flabs.sucuri.net\u002F?is-my-wordpress-ddosing\" rel=\"nofollow ugc\">Sucuri’s WordPress DDOS Scanner\u003C\u002Fa> to check if your site is DDOS’ing other websites\u003C\u002Fp>\n\u003Ch4>Why Not Just Disable XMLRPC Altogether?\u003C\u002Fh4>\n\u003Cp>Yes, you can choose to do that, but if you use popular plugins like JetPack (that use XMLRPC) then those plugins will stop working. That is why this small plugin exists.\u003C\u002Fp>\n","Prevent pingback, XML-RPC and denial of service DDOS attacks by disabling the XML-RPC pingback functionality.",9000,94267,60,6,"2023-07-24T23:03:00.000Z","6.3.8","5.2","5.6",[92,93,71,94,21],"disable-ping","ping","xml-rpc","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fremove-xmlrpc-pingback-ping","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fremove-xmlrpc-pingback-ping.1.6.zip",{"slug":98,"name":99,"version":100,"author":101,"author_profile":102,"description":103,"short_description":104,"active_installs":105,"downloaded":106,"rating":85,"num_ratings":14,"last_updated":107,"tested_up_to":108,"requires_at_least":109,"requires_php":18,"tags":110,"homepage":116,"download_link":117,"security_score":32,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":26},"manage-xml-rpc","Manage XML-RPC","1.0.2","brainvireinfo","https:\u002F\u002Fprofiles.wordpress.org\u002Fbrainvireinfo\u002F","\u003Cp>You can now disable XML-RPC to avoid Brute force attack for given IPs or can even enable access for some IPs. XML-RPC on WordPress is actually an API that gives developers who build mobile apps, desktop apps and other services, the ability to talk to a WordPress site. The XML-RPC API that WordPress provides gives developers, a way to write applications (for you) that can do many of the things that you can do when logged into WordPress via the web interface.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cp>Block XML-RPC by following way.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Disable pingback.ping, pingback.extensions.getPingbacks and Unset X-Pingback from HTTP headers, that will block bots to access specified method.\u003C\u002Fli>\n\u003Cli>Disable\u002FBlock XML-RPC for all users.\u003C\u002Fli>\n\u003C\u002Ful>\n","Enable\u002FDisable XML-RPC for all or based on IP list, also you can control pingback and Unset X-Pingback from HTTP headers.",6000,64108,"2024-12-02T07:10:00.000Z","6.7.5","4.0",[111,112,113,114,115],"block-xml-rpc","brute-force-attacks","security","xml-rpc-pingback","xmlrpc-php-attack","http:\u002F\u002Fwww.brainvire.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmanage-xml-rpc.1.0.2.zip",{"slug":119,"name":120,"version":121,"author":122,"author_profile":123,"description":124,"short_description":125,"active_installs":105,"downloaded":126,"rating":54,"num_ratings":14,"last_updated":127,"tested_up_to":49,"requires_at_least":128,"requires_php":129,"tags":130,"homepage":18,"download_link":134,"security_score":54,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":26},"stop-xml-rpc-attacks","Stop XML-RPC Attacks","2.0.0","Pascal CESCATO","https:\u002F\u002Fprofiles.wordpress.org\u002Fpcescato\u002F","\u003Cp>Stop XML-RPC Attacks protects your WordPress site from XML-RPC brute force attacks, DDoS attempts, and reconnaissance probes while maintaining compatibility with essential services like Jetpack and WooCommerce.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Three security modes: Full Disable, Guest Disable, or Selective Blocking\u003C\u002Fli>\n\u003Cli>Blocks dangerous methods: system.multicall, pingback.ping, and more\u003C\u002Fli>\n\u003Cli>Compatible with Jetpack and WooCommerce\u003C\u002Fli>\n\u003Cli>Optional user enumeration blocking\u003C\u002Fli>\n\u003Cli>Attack logging for monitoring\u003C\u002Fli>\n\u003Cli>Zero configuration required – works out of the box\u003C\u002Fli>\n\u003Cli>Clean, intuitive admin interface\u003C\u002Fli>\n\u003C\u002Ful>\n","Blocks dangerous XML-RPC methods while preserving Jetpack, WooCommerce, and mobile apps compatibility.",26717,"2026-01-01T13:41:00.000Z","6.0","7.4",[131,132,133,113,21],"brute-force","ddos","jetpack","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fstop-xml-rpc-attacks.2.0.0.zip",{"attackSurface":136,"codeSignals":212,"taintFlows":258,"riskAssessment":296,"analyzedAt":306},{"hooks":137,"ajaxHandlers":204,"restRoutes":205,"shortcodes":206,"cronEvents":207,"entryPointCount":24,"unprotectedCount":24},[138,144,146,148,150,152,154,159,162,166,169,173,177,181,184,188,192,196,200,202],{"type":139,"name":140,"callback":141,"file":142,"line":143},"filter","redirect_post_location","anonymous","includes\\class-wp-xmlrpc-client.php",138,{"type":139,"name":140,"callback":141,"file":142,"line":145},141,{"type":139,"name":140,"callback":141,"file":142,"line":147},144,{"type":139,"name":140,"callback":141,"file":142,"line":149},147,{"type":139,"name":140,"callback":141,"file":142,"line":151},150,{"type":139,"name":140,"callback":141,"file":142,"line":153},237,{"type":155,"name":156,"callback":156,"file":157,"line":158},"action","init","push-syndication.php",35,{"type":155,"name":160,"callback":160,"file":157,"line":161},"admin_init",36,{"type":155,"name":163,"callback":164,"file":157,"line":165},"admin_menu","register_syndicate_settings",39,{"type":155,"name":167,"callback":168,"file":157,"line":66},"save_post","save_site_settings",{"type":155,"name":170,"callback":171,"file":157,"line":172},"admin_enqueue_scripts","load_scripts_and_styles",45,{"type":139,"name":174,"callback":175,"file":157,"line":176},"post_updated_messages","push_syndicate_admin_messages",48,{"type":155,"name":178,"callback":179,"file":157,"line":180},"add_meta_boxes","add_post_metaboxes",51,{"type":155,"name":167,"callback":182,"file":157,"line":183},"save_syndicate_settings",52,{"type":155,"name":185,"callback":186,"file":157,"line":187},"wp_trash_post","delete_slave_posts",53,{"type":155,"name":189,"callback":190,"file":157,"line":191},"transition_post_status","schedule_syndicate_content_cron",56,{"type":155,"name":193,"callback":194,"file":157,"line":195},"syn_syndicate_content","syndicate_content",57,{"type":155,"name":197,"callback":198,"file":157,"line":199},"syn_delete_content","delete_content",58,{"type":139,"name":140,"callback":141,"file":157,"line":201},429,{"type":139,"name":140,"callback":141,"file":157,"line":203},435,[],[],[],[208,210],{"hook":193,"callback":193,"file":157,"line":209},581,{"hook":197,"callback":197,"file":157,"line":211},830,{"dangerousFunctions":213,"sqlUsage":229,"outputEscaping":232,"fileOperations":24,"externalRequests":86,"nonceChecks":256,"capabilityChecks":230,"bundledLibraries":257},[214,217,218,219,220,221,222,227,228],{"fn":215,"file":142,"line":143,"context":216},"create_function","add_filter('redirect_post_location', create_function( '$location', 'return add_query_arg(\"message\", ",{"fn":215,"file":142,"line":145,"context":216},{"fn":215,"file":142,"line":147,"context":216},{"fn":215,"file":142,"line":149,"context":216},{"fn":215,"file":142,"line":151,"context":216},{"fn":215,"file":142,"line":153,"context":216},{"fn":223,"file":224,"line":225,"context":226},"unserialize","includes\\push-syndicate-encryption.php",16,"return @unserialize( $data );",{"fn":215,"file":157,"line":201,"context":216},{"fn":215,"file":157,"line":203,"context":216},{"prepared":230,"raw":24,"locations":231},5,[],{"escaped":233,"rawEcho":234,"locations":235},41,10,[236,240,241,242,244,246,248,250,252,254],{"file":237,"line":238,"context":239},"includes\\class-wp-rest-client.php",231,"raw output",{"file":157,"line":153,"context":239},{"file":157,"line":153,"context":239},{"file":157,"line":243,"context":239},238,{"file":157,"line":245,"context":239},257,{"file":157,"line":247,"context":239},314,{"file":157,"line":249,"context":239},315,{"file":157,"line":251,"context":239},370,{"file":157,"line":253,"context":239},375,{"file":157,"line":255,"context":239},393,3,[],[259,286],{"entryPoint":260,"graph":261,"unsanitizedCount":284,"severity":285},"get_api_token (push-syndication.php:279)",{"nodes":262,"edges":279},[263,268,273,276],{"id":264,"type":265,"label":266,"file":157,"line":267},"n0","source","$_GET",304,{"id":269,"type":270,"label":271,"file":157,"line":247,"wp_function":272},"n1","sink","echo() [XSS]","echo",{"id":274,"type":265,"label":275,"file":157,"line":267},"n2","$_GET (x3)",{"id":277,"type":270,"label":271,"file":157,"line":278,"wp_function":272},"n3",327,[280,282],{"from":264,"to":269,"sanitized":281},false,{"from":274,"to":277,"sanitized":283},true,1,"medium",{"entryPoint":287,"graph":288,"unsanitizedCount":24,"severity":295},"\u003Cpush-syndication> (push-syndication.php:0)",{"nodes":289,"edges":293},[290,292],{"id":264,"type":265,"label":291,"file":157,"line":267},"$_GET (x4)",{"id":269,"type":270,"label":271,"file":157,"line":247,"wp_function":272},[294],{"from":264,"to":269,"sanitized":283},"low",{"summary":297,"deductions":298},"The push-syndication plugin v1.0 exhibits a generally good security posture with a small attack surface and a lack of recorded vulnerabilities. The static analysis shows that all identified entry points (AJAX handlers, REST API routes, and shortcodes) are either absent or have proper authentication and permission checks.  Furthermore, all SQL queries are securely prepared, and the majority of output is properly escaped, indicating adherence to common WordPress security best practices.  The absence of known CVEs and historical vulnerabilities further strengthens this positive assessment.\n\nHowever, there are areas of concern that warrant attention. The presence of dangerous functions like `create_function` and `unserialize` introduces potential risks, especially if they are used with user-supplied input.  While the taint analysis did not reveal critical or high severity issues, one flow with unsanitized paths suggests a potential for unexpected behavior or information disclosure if not handled carefully. The use of external HTTP requests also presents a minor risk, as these can be susceptible to various attacks if not properly validated and sanitized.\n\nIn conclusion, push-syndication v1.0 is a relatively secure plugin, primarily due to its limited attack surface and strong track record. The plugin developers have implemented several security controls effectively. However, the use of legacy dangerous functions and the single identified unsanitized path represent weaknesses that could be exploited. Addressing these specific code signals would further enhance the plugin's overall security.",[299,301,303],{"reason":300,"points":234},"Dangerous functions found: create_function, unserialize",{"reason":302,"points":230},"Flow with unsanitized paths detected",{"reason":304,"points":305},"External HTTP requests present",2,"2026-03-16T21:18:31.136Z",{"wat":308,"direct":314},{"assetPaths":309,"generatorPatterns":311,"scriptPaths":312,"versionParams":313},[310],"\u002Fwp-content\u002Fplugins\u002Fpush-syndication\u002Fcss\u002Fsites.css",[],[],[],{"cssClasses":315,"htmlComments":316,"htmlAttributes":332,"restEndpoints":333,"jsGlobals":334,"shortcodeOutput":335},[],[317,318,319,320,321,322,323,324,325,326,327,328,329,330,331],"\u003C!-- @TODO define a new capability to push syndicate -->","\u003C!-- @TODO check add add_settings_field args -->","\u003C!-- @TODO add help using contextual_help -->","\u003C!-- @TODO mark helper functions as private? -->","\u003C!-- @TODO check sites are publicly queryable -->","\u003C!-- @TODO add options to retry delete_error_sites -->","\u003C!-- @TODO we need a menu icon here -->","\u003C!-- @TODO check this -->","\u003C!-- @TODO match capabilities with custom capabilities -->","\u003C!-- @TODO define more parameters -->","\u003C!-- Post Type Configuration -->","\u003C!-- select post types -->","\u003C!-- Delete Pushed Posts -->","\u003C!-- delete pushed posts -->","\u003C!-- API Token Configuration -->",[],[],[],[]]