Regardless of your blanket dismissal of the risks – it IS a very large security hole that is often exploited by hackers, so on sites who do not need its functionality, it absolutely makes sense to disable it.
But that is what the whitelisting feature in the Wordfence firewall is for – to allow you to tailor your firewall needs with your site’s user requirements.
]]>So Wordfence doesn’t inherently disable XML-RPC, so something else is causing the blockage… (probably still requiring a tweak to the WF firewall, though…)
If you go to the Live Traffic section of Wordfence and choose the “Blocked by Firewall” filter, do you see any entries where JetPack is being blocked?
If so, you should be able to choose “Whitelist Param from Firewall” to disable the block and whitelist that type of request.
Thanks.
]]>