Web-Art Login Shield with reCAPTCHA vs XML-RPC Settings

Web-Art Login Shield with reCAPTCHA protects WordPress authentication, Elementor Login widgets and Elementor Forms. It provides optional Google reCAPTCHA v2/v3, IP lockouts, Advanced login URL protection, IP blocking and REST/XML-RPC protection. It preserves WordPress core authentication logic. No ads, author telemetry or external dashboard. All modules are opt-in and disabled by default. Key Features reCAPTCHA v2/v3 selectable v2 checkbox or v3 score-based verification protection for wp-login.php, Elementor Login and Elementor Forms server-side token, action, score and hostname validation where applicable configurable v3 score threshold one active type at a time configuration verification before activation Elementor support protection for Elementor Login and Elementor Pro Forms native Elementor reCAPTCHA fields are skipped to avoid duplication v2 alignment controls login errors and lockouts remain inside the Login widget dynamic content and Elementor popup support Login Protect per-IP failed-attempt counting and temporary lockouts safe concurrent-request handling active-lockout countdown local security event log with bounded retention optional REST API, Application Password and XML-RPC protection independent operation with or without reCAPTCHA Advanced login URL optional custom login endpoint protection of default login routes while preserving required public actions logout and password-link compatibility emergency wp-config.php recovery constant IP allowlists and blocking separate reCAPTCHA allowlist and Login Protect trusted IP list permanent IP blocking for public site requests with HTTP 403 optional IP | reason notes XML-RPC hardening Optional blocking of: pingback.ping pingback.extensions.getPingbacks system.multicall Security Model Protected flows use fail-closed handling. If an enabled check cannot be completed safely, the request is rejected instead of bypassing protection. Login Protect preserves active lockouts and safely handles concurrent requests. Setting Maximum login attempts or Lockout duration to 0 disables lockout enforcement. All modules remain disabled until enabled. Recovery constants are available in wp-config.php for selected modules. External Services This plugin integrates with Google reCAPTCHA v2 and v3, services provided by Google LLC. reCAPTCHA is disabled by default. Google scripts or verification requests are used only after an administrator enables reCAPTCHA or runs a settings-page verification test. Google’s reCAPTCHA JavaScript (https://www.google.com/recaptcha/api.js) may load on protected wp-login.php requests, pages containing protected Elementor widgets or forms, and the settings page during a verification test. Allowlisted visitors bypass frontend loading where applicable. When reCAPTCHA runs, the visitor’s browser connects directly to Google. Google may process browser, device and interaction information and may set the necessary _GRECAPTCHA cookie under its policies. For server-side verification, the plugin sends the token, configured Secret Key and visitor IP address when available to Google’s siteverify endpoint. It does not include usernames, passwords, email addresses or form contents in that request. The plugin sends no telemetry, analytics or usage data to its author. Google policies: https://policies.google.com/privacy https://policies.google.com/terms Privacy Locally stored security data may include: IP addresses, failed-attempt counts and lockout timestamps a username or email associated with an IP lockout recent events containing an IP address, username or email, source, type and timestamp the latest reCAPTCHA configuration or transport error used for diagnostics permanent IP blocklist entries and optional notes Inactive Login Protect entries become eligible for deletion after seven days. Active lockouts remain until expiry. The event log is limited to 30 entries and 30 days. WordPress privacy tools export or erase records matched to the requested email address or associated account. Unmatched IP-only records remain subject to retention and administrator cleanup. Permanent blocklist entries remain until removed by an administrator. Plugin data can be removed during uninstall when uninstall cleanup is enabled. Legal reCAPTCHA is a trademark of Google LLC. Elementor is a trademark of Elementor Ltd. This plugin is not affiliated with, endorsed by, or sponsored by Google LLC or Elementor Ltd.

XML-RPC Settings Configure XML-RPC methods to increase the security of your website: Build-in features could be used for malicious purposes and cannot be disabled by default. Disable GET access XML-RPC API only responds to POST requests. Direct GET access is not needed and can be used to fingerprint websites and use them as XML-RPC zombies in later attacks. Disable system.multicall system.multicall method can be misused for amplification attacks. Disable system.listMethods system.listMethods method can be used for verifying attack scope. Prevent malicious actors from enumerating usernames and credentials. Disable authenticated methods Methods requiring authentication, such as wp.getUsersBlogs, are often used to brute-force your passwords. Pingbacks are a helpful feature to discover back-links to your posts but can be misused for DDoS attacks or allow fingerprinting your WP version. Disable pingbacks Pingbacks are generally safe, but are often used for DDoS attacks via system.multicall. Remove X-Pingback header If you decide to disable pingbacks, it’s a good practice to remove the X-Pingback header return by your posts. Hide WordPress version when verifying pingbacks Pingbacks’ user-agent can reveal your exact WordPress version, even when hidden by other plugins. Hide WordPress version when sending pingbacks Pingbacks’ user-agent can reveal your exact WordPress version, even when hidden by other plugins. Unnecessary XML-RPC API, leave enabled if you are not sure. Disable Demo API Remove demo.sayHello and demo.addTwoNumbers methods, as they are not needed. Disable Blogger API WordPress supports the Blogger XML-RPC API methods. Disable MetaWeblog API WordPress supports the metaWeblog XML-RPC API. Disable MovableType API WordPress supports the MovableType XML-RPC API. If you are using some integrations or WP mobile applications, it might be a good idea to allow XML-RPC only to specific IPs. Allow XML-RPC only for IP comma separated eg. 192.168.10.242, 192.168.10.241 It is possible to hide a message between the allowed methods when system.listMethods is called (not recommended). Add message to XML-RPC methods We are hiring! Check jobs.yourdomains.com