by Eric Mann 3.7 (3 reviews)

Secure XML-RPC

Name: Secure XML-RPC
Rating: 3.7 (3 reviews)
Author: Eric Mann

More secure wrapper for the WordPress XML-RPC interface.

Secure XML-RPC ranks #20,666 among WordPress.org plugins with 50+ active installations, is #459 of 1,584 in the Authentication category, a 3.7/5 rating from 3 reviews, and was last updated Aug 30, 2014. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 4 (Current: 7.1)

v1.0.0 Current Version v1.0.0

Updated 12 years ago Last Update on 30 Aug, 2014

Refreshed 6 hours ago Last Refreshed on

#459 of 1,584 in Authentication Top 50% by installs No update in over a year

View on WordPress.org

Rank

#20,666

+42 this week

Active Installs

50+

-9.1%

KW Avg Position

122

— No change

Downloads

6.9K

+1 today

Support Resolved

— No change

Rating

74%

Review 3.7 out of 5

3.7 (3 reviews)

Next Milestone 60

Total Progress 50%

50+ 60+

1,768

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 5 more installs to reach 60+

Rank Changes

Current #20,666

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

3.7

3 reviews

Overall 74%

2 (67%)

0 (0%)

1 (33%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.0.0
Last Updated: Aug 30, 2014
Requires WP: 3.8+
Tested Up To: 4
PHP Version: N/A
Author: Eric Mann

Support & Rating

Rating: ★ ★ ★ ★ ☆ 3.7
Reviews: 3
Support Threads: 0
Resolved: 0%

Keywords

authentication oauth security xmlrpc

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,754

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,007

WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More

5M+ installs

Wordfence Security – Firewall, Malware Scan, and Login Security

Limit Login Attempts Security – Login Security, 2FA, Firewall, Brute Force Prevention

All-In-One Security (AIOS) – Security and Firewall

1M+ installs

#62

MainWP Child – Securely Connects to the MainWP Dashboard to Manage Multiple Sites

700K+ installs

#86

View all Authentication plugins

Frequently Asked Questions

Common questions about Secure XML-RPC

The old username/password paradigm can still be used, but will result in a X-Deprecated header being returned by the server. From now on, you will send an Authorization header. This header will be the publishing application's public key, two pipe (|) characters, and a hash of the application's secret key concatenated with the body of the request.

Say your application has the following information: * Public Key: b730db0864b0d4453ba6a26ad6613cd4 * Secret Key: 7647a19f5bf3e9fd001419900ad48a54 And you want to make the following request (whitespace/indentation added for readability, but is removed when calculating hashes): <?xml version="1.0"?> <methodCall> <methodName>wp.getPosts</methodName> <params> <param> <value><i4>1</i4></value> </param> <param> <value><string></string></value> </param> <param> <value><string></string></value> </param> </params> </methodCall> Note that the second and third parameters (traditionally username and password) are empty. Usernames and passwords can still be specified, but will result in the server returning an X-Deprecated header. Your Authorization header would thus become: b730db0864b0d4453ba6a26ad6613cd4||3fac15f99f7a178f922bcc4942e62dc9001b2a45118fc3a6f3aebd77d25f4d58 The second part of the header is generated in PHP by calculating: hash( 'sha256', '7647a19f5bf3e9fd001419900ad48a54' . hash( 'sha256', '7647a19f5bf3e9fd001419900ad48a54' . {request_body} ) ) WordPress will read the header and log you in as usual, but you never need to send your password across the wire. In this paradigm, application secret keys should also be treated as passwords - they are sensitive information!

Some developers raised concerns about length extension attacks in previous editions of the plugin. While length extension isn't strictly necessary when dealing with XML-based messaging, a double hash helps end the discussion around potentially-related vulnerabilities. The double-hash is similar to but simpler than HMAC and is fairly easy to implement in any programming language. Just note, PHP's hash() function returns a base64-encoded string, not a raw hash of the data passed in.

Not necessarily. The latest version of the plugin adds a new XML-RPC method to the system that allows for the generation of user-specific application keys remotely. Please only ever call this method over a secure/trusted network connection when setting up an application for the first time.