| CARVIEW |
Home / Plugin: Disable XML-RPC / WordPress Lists Disable XML-RPC as no longer maintained
WordPress lists this plugin as no longer maintained as seen at https://wordpress.org/plugins/disable-xml-rpc/. WordFence therefore flags it as a security vulnerability.
The page I need help with: [log in to see the link]
I came here for the same reason. Wordfence is flagging as abandoned for me.
Is this plugin still maintained? Will there be a new version of it pushed anytime soon?
Thanks!
Good morning/afternoon/evening everyone!
See my post from two years ago – https://wordpress.org/support/topic/disable-xml-rpc-is-still-alive/.
Everything is still status quo, including my very terrible ability to update the readme file on a regular basis after doing my usual testing with each new version.
I’ve just pushed a new readme to note the latest testing, to keep WordFence happy. Apologies for the continued delays! It’s still the simplest and cleanest plugin to disable XML-RPC, if that’s all you need to do.
Hi. I have auto updates for plugins off, but when I logged in to update, it looks like it’s already updated in the plugin list to V 1.0.1 – how is that possible? Thanks for resolving the issue so quickly with the Wordfence flag.
emgb_520.
I didn’t update the version number – because nothing in the actual code changed, just the readme file. It’s been v1.0.1 since 2015 – and even that change was just cleaning up some blank lines from the file. If you look at the actual code for the plugin on your site, it probably hasn’t pulled the newest readme – WordFence is just comparing your version number against the WordPress plugin repo and noting that it’s currently maintained.
The plugin is so simple – it’s one actual line of code that just sets a flag in WordPress that was introduced in WordPress 3.5 when they removed a toggle for the XML-RPC setting from the interface. It’s done it’s job as simply as possible since 2012!
Thanks – I will just trust that everything is kosher, as I’m not entirely comprehending how Wordfence “sees that it is still maintained” when the version number hasn’t changed in 10 years. LOL.
It’s not getting flagged anymore, though.
emgb_520.
Haha fair, it’s definitely not intuitive about how it’s doing that. It’s looking to the WordPress.org website to see that the current readme file for the plugin says that it’s compatible with the current version of WordPress. It sees that and that the version number of the plugin you have matches what’s on the website and says it’s all good.
You must be logged in to reply to this topic.
