Adds REST API & XML-RPC brute force protection and real-time email alerts. No configuration is changed automatically \u2014 visit Settings \u2192 IC Security Guard to enable the new options.<\/p>","1.0.0":"
Initial release of IC Security Guard.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3625724,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3625724,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.jpg":{"filename":"banner-1544x500.jpg","revision":3625734,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.jpg":{"filename":"banner-772x250.jpg","revision":3625734,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.2.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3625724,"resolution":"1","location":"assets","locale":"","width":1895,"height":867},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3625724,"resolution":"2","location":"assets","locale":"","width":1910,"height":857}},"screenshots":{"1":"Backend settings","2":"Change Login Url","3":"Readme"}},"plugin_section":[],"plugin_tags":[2439,1229,23853,600,1909],"plugin_category":[54],"plugin_contributors":[168627],"plugin_business_model":[],"class_list":["post-337793","plugin","type-plugin","status-publish","hentry","plugin_tags-brute-force","plugin_tags-login-security","plugin_tags-rest-api","plugin_tags-security","plugin_tags-two-factor-authentication","plugin_category-security-and-spam-protection","plugin_contributors-itclan","plugin_committers-itclan"],"banners":{"banner":"https:\/\/ps.w.org\/ic-security-guard\/assets\/banner-772x250.jpg?rev=3625734","banner_2x":"https:\/\/ps.w.org\/ic-security-guard\/assets\/banner-1544x500.jpg?rev=3625734","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/ic-security-guard\/assets\/icon-128x128.png?rev=3625724","icon_2x":"https:\/\/ps.w.org\/ic-security-guard\/assets\/icon-256x256.png?rev=3625724","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/ic-security-guard\/assets\/screenshot-1.png?rev=3625724","caption":"Backend settings"},{"src":"https:\/\/ps.w.org\/ic-security-guard\/assets\/screenshot-2.png?rev=3625724","caption":"Change Login Url"}],"raw_content":"\n
IC Security Guard is a lightweight, all-in-one security hardening plugin that protects your WordPress site from brute force login attacks, REST API abuse, and XML-RPC amplification attacks \u2014 and keeps your site owner informed in real time when an attack is blocked.<\/p>\n\n
Instead of leaving Hide Default Login Page<\/strong><\/p>\n\n Login Attempt Limiting & Lockout<\/strong><\/p>\n\n Email OTP Two-Factor Authentication<\/strong><\/p>\n\n REST API & XML-RPC Brute Force Protection<\/strong><\/p>\n\n Real-time Email Alerts<\/strong><\/p>\n\n You can always reach your site's database (via phpMyAdmin or your host) and update the Logged-in users are always allowed through to No. Logged-in users pass through untouched. The hidden login, lockout, REST API, and XML-RPC protections only apply to unauthenticated visitors and failed authentication attempts.<\/p><\/dd>\n Lockout state is stored per IP address using WordPress transients, so it persists across page reloads and works with whatever caching layer your site already uses. The same lockout state is shared by the login form, the REST API, and XML-RPC.<\/p><\/dd>\n When enabled, after a user enters the correct username and password, they are redirected to a dedicated verification page and emailed a 6-digit code (sent to their WordPress account email address). The code must be entered within the configured expiry window to complete login. Codes can be resent with a short cooldown between requests, and login only completes after the correct code is verified. This step is automatically skipped for REST API and XML-RPC requests, since application passwords and API integrations authenticate programmatically and have no page to display a challenge on.<\/p><\/dd>\n XML-RPC's By default, WordPress's REST API exposes a list of registered usernames at No. Real-time email alerts are sent once per alert type whenever an event first triggers, then suppressed for the configured cooldown period (15 minutes by default) even if the same type of event keeps happening. This keeps you informed without flooding your inbox during a sustained attack.<\/p><\/dd>\n Those sections are currently marked \"Coming soon\" in the plugin settings and will be added in a future release.<\/p><\/dd>\n\n<\/dl>\n\n\nwp-login.php<\/code>, \/wp-admin<\/code>, xmlrpc.php<\/code>, and the REST API open for anyone to probe, IC Security Guard lets you move your login page to a custom secret URL, lock out anyone who fails to log in too many times, require a one-time email code before login completes, shut down common XML-RPC and REST API attack vectors, and get emailed the moment something is blocked.<\/p>\n\nSpecial Features<\/h4>\n\n
\n
wp-login.php<\/code> and \/wp-admin<\/code> login pages from unauthenticated visitors<\/li>\n\n
\n
\n
system.multicall<\/code>-based amplification attacks that let attackers test hundreds of password combinations in a single request<\/li>\n\/wp-json\/wp\/v2\/users<\/code>) so attackers cannot harvest valid usernames<\/li>\n\n
\n
\/wp-content\/plugins\/<\/code> directory, or install the plugin directly through the WordPress Plugins screen.<\/li>\n\n
\n
What happens if I forget my new login URL?<\/h3><\/dt>\n
icsegu_hidelogin_options<\/code> option in the wp_options<\/code> table to disable hide_login_url<\/code>, restoring access to the default wp-login.php<\/code>.<\/p><\/dd>\nWill this lock me out of my own site?<\/h3><\/dt>\n
\/wp-admin<\/code> regardless of the hidden login setting. The failed-login lockout only applies to failed authentication attempts, and resets automatically once the configured lockout duration passes.<\/p><\/dd>\nDoes this plugin affect logged-in users?<\/h3><\/dt>\n
Where is the lockout state stored?<\/h3><\/dt>\n
How does Email OTP Two-Factor Authentication work?<\/h3><\/dt>\n
What does disabling XML-RPC protect against?<\/h3><\/dt>\n
system.multicall<\/code> method allows an attacker to test many username\/password combinations in a single HTTP request, bypassing typical per-request throttling. Enabling \"Disable XML-RPC\" turns off the XML-RPC endpoint entirely. If you rely on XML-RPC for a mobile app, Jetpack, or another integration, leave this option off \u2014 any failed XML-RPC login attempts are still covered by the shared lockout.<\/p><\/dd>\nWhat does blocking REST API user enumeration protect against?<\/h3><\/dt>\n
\/wp-json\/wp\/v2\/users<\/code> to anyone, even when logged out. Attackers use this to harvest valid usernames before a brute-force attempt. Enabling \"Block REST API User Enumeration\" returns an authorization error for unauthenticated requests to this endpoint, while logged-in requests are unaffected.<\/p><\/dd>\nWill I get an email for every single failed login?<\/h3><\/dt>\n
Is .htaccess or wp-config.php hardening included?<\/h3><\/dt>\n
1.2.0<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n