Uğur Biçer

fyndsoft

SecureFusion acts as a robust shield against many common attack types, including login attempts and DDoS attacks via XML-RPC. 
It not only enhances security but also significantly improves your site’s performance. 
By helping to prevent unauthorized access and collection of sensitive information from your site, it neutralizes many attack vectors. 
This is an effective solution for ensuring user safety and maintaining the speed of your site.
Features:
<h4>XMLRPC</h4>
SecureFusion aids in managing your critical XML-RPC services, often a prime target for WordPress hack attempts and spam comments. 
The plugin allows you to selectively disable specific XML-RPC services, defending your site from XML-RPC attacks like spam comments without entirely disabling all XML-RPC services. 
However, be aware that blocking all XML-RPC requests may impact the interaction of certain applications and services with WordPress.
<ul>
<li>
XML-RPC FULL PROTECTION (Disable all XML-RPC) 
This feature blocks all incoming XML-RPC requests, offering an effective countermeasure against various remote attacks. 
Remember, this might impact certain functionalities that rely on XML-RPC.
</li>
<li>
XML-RPC LOGIN PROTECTION 
This feature denies remote login requests made via XML-RPC, providing an extra line of defense against brute force login attempts.
</li>
<li>
XML-RPC PINGBACK PROTECTION 
This feature blocks remote pingback requests, assisting in the prevention of DDoS attacks.
</li>
<li>
SELF PINGBACK PROTECTION 
This feature prevents remote self pingback requests, further strengthening your defenses against DDoS attacks.
</li>
</ul>
<h4>SSL</h4>
SecureFusion facilitates SSL integration into your site, provided you have an SSL certificate purchased from any SSL dealer or acquired through a free SSL service like Cloudflare. 
The plugin forces the redirection of selected zone URLs on your site to HTTPS/SSL. 
Note that SSL certificates must always be valid and correctly configured; otherwise, users may face issues accessing the site.
<ul>
<li>
Enable HTTPS / SSL 
Enforces the use of HTTPS/SSL across your site, ensuring that data is encrypted during transmission.
</li>
<li>
Force HTTPS Login 
Redirects login page protocol from HTTP to HTTPS.
</li>
<li>
Force HTTPS Admin 
Redirects admin page protocol from HTTP to HTTPS.
</li>
<li>
Force HTTPS Front Page 
Redirects front page protocol from HTTP to HTTPS.
</li>
</ul>
<h4>Login</h4>
<ul>
<li>
Login Attempt Limit 
Set the maximum number of login attempts and the waiting time after reaching this limit to prevent brute force attacks on your login page.
</li>
<li>
Change Login Error 
SecureFusion allows you to modify default login errors, making it harder for potential attackers to gather information.
</li>
<li>
Change Admin Username 
This feature lets you change your administrator’s username (e.g., the default ‘admin’ username), making it more difficult to guess user credentials. This provides an obscurity layer rather than direct protection from SQL vulnerabilities. (Note: This changes the username, not the numerical User ID).
</li>
<li>
New Custom Login URL 
This feature lets you change your login page URL name. 
Be aware that if your site uses SSL/HTTPS, ensure your overall SSL configuration is correct and all resources load securely after any URL changes to avoid potential issues.
</li>
</ul>
<h4>Firewall</h4>
<ul>
<li>
Filter Bad Requests 
The plugin helps secure your site against various attacks such as XSS, CSRF, and Code Injections.
</li>
<li>
Disable Rest API 
SecureFusion helps safeguard sensitive information by allowing you to disable REST API endpoints, which can prevent them from being used by attackers for information disclosure or exploitation. 
However, keep in mind that disabling the REST API can restrict the functionality of your WordPress site since some plugins and themes depend on it.
</li>
</ul>
For complete information, please visit our website <a href="https://fyndsoft.com/securefusion" rel="nofollow ugc">the SecureFusion website</a>.

SecureFusion: Ultimate Security – Firewall, SSL Control, Anti Spam, Login Security

Firewall, XML-RPC Security, Spam Protection, Redirect HTTP traffic to HTTPS, Login Page Security.

Amin Nazemi

Neatma

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.
PLUGIN FEATURES 
(These are options you can enable or disable each one)
<ul>
<li>Disable access to xmlrpc.php file using .httacess file </li>
<li>Automatically change htaccess file permission to read-only (0444)</li>
<li>Disable X-pingback to minimize CPU usage </li>
<li>Disable selected methods from XML-RPC</li>
<li>Remove pingback-ping link from header</li>
<li>Disable trackbacks and pingbacks to avoid spammers and hackers</li>
<li>Rename XML-RPC slug to whatever you want</li>
<li>Black list IPs for XML-RPC</li>
<li>White list IPs for XML-RPC</li>
<li>Some options to speed-up your wordpress website</li>
<li>Disable JSON REST API</li>
<li>Hide WordPress Version</li>
<li>Disable built-in WordPress file editor</li>
<li>Disable wlw manifest</li>
<li>And some other options</li>
</ul>
What is XMLRPC
XML-RPC, or XML Remote Procedure Call is a protocol which uses XML to encode its calls and HTTP as a transport mechanism. 
Beginning in WordPress 3.5, XML-RPC is enabled by default. Additionally, the option to disable/enable XML-RPC was removed. For various reasons, site owners may wish to disable this functionality. This plugin provides an easy way to do so.
Why you should disable XML-RPC 
Xmlrpc has two main weaknesses
<ul>
<li>Brute force attacks: 
Attackers try to login to WordPress using xmlrpc.php with as many username/password 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.”</li>
<li>Denial of Service Attacks via Pingback: 
Back 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.”</li>
</ul>

Disable XML-RPC-API

The upgrade notice keeps coming back on every screen even after being dismissed. It looks very unprofessional to my clients and is embarrassing for me as a web developer, i would rather disable the plugin and use the code in a function. 

It should be permanently dismissible via a cookie, like for other plugins. It might be ok once, when the plugin is first installed or updated, but after that, it should never appear again. 

Good plugin, but upgrade nag is too annoying

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

SecureFusion: Ultimate Security – Firewall, SSL Control, Anti Spam, Login Security vs Disable XML-RPC-API