xpay✦ Commerce
Directory
WooCommerce plugins
Open24 Security
Open24 Security
Security hardening for WordPress and WooCommerce: lock down the REST API, protect the login, hide version info and add security headers.
5.0
(1 ratings)Will this break my store?
What the WordPress.org registry says about keeping Open24 Security running.
Tested to 7.0.5 — 1 branch behind 7.1
Tested against the WordPress branch in use today.1 month ago
7.4
Your host must be running at least this version.5.5
1
A single maintainer. Worth knowing if the plugin is load-bearing for your store.Maintenance & trust
Scored on how Open24 Security is looked after — not on how many stores run it.
Maintenance
35 / 35WordPress compatibility
20 / 20Support responsiveness
Not enough dataMerchant satisfaction
10 / 15Listing transparency
6 / 10Ratings
5.0
1 ratingOpen24 Security applies a set of well-known hardening measures to WordPress and WooCommerce sites from a single settings screen. Every option is off by default and can be switched on individually, so you decide exactly how much you want to restrict.
The plugin does not phone home, does not require an account and does not send any data to external services. The only outbound request it makes is to the official WordPress.org API, and only when you explicitly rotate your security keys.
Features
WordPress REST API
- Hide the /wp-json/wp/v2/users endpoint
- Require authentication on sensitive endpoints
- Disable the /wp-json/ index
Login
- Custom login URL (replace wp-login.php with your own slug)
- Limit login attempts per IP address
- Block common usernames such as admin or root
- Hide error hints that reveal whether a username exists
Protocols
- Disable XML-RPC
- Block external access to wp-cron.php
- Block user enumeration via ?author=N
Information disclosure
- Hide the WordPress version from the generator meta tag and RSS feeds
HTTP security headers
- X-Frame-Options, X-Content-Type-Options, Referrer-Policy
- Permissions-Policy, X-XSS-Protection
- Optional HSTS
WooCommerce
- Reject anonymous requests to the /wc/v3/ and /wc/v2/ REST routes
- Hide WooCommerce headers on the storefront
Tools
- Log out all users: rotates the WordPress security keys and salts, which invalidates every session cookie and immediately signs out all logged-in users. Useful after a suspected compromise or when an employee leaves.
- Change log: records which settings were changed and when.
Agency signature
- Adds an Open24 signature in the document head so the site can be identified as maintained by the agency by crawlers such as BuiltWith. This can be turned off.
About the security keys feature
Rotating the WordPress security keys requires updating the corresponding constants in wp-config.php. The plugin does this through the official WP_Filesystem API, writes to a temporary file with restrictive permissions and then moves it over the original in a single atomic operation, preserving the original file permissions. No backup copy is left anywhere on the server, and if any step fails, wp-config.php is left untouched.
If wp-config.php is not writable, the feature reports it and makes no changes.
Every option is off by default. The ones that need the most care are the custom login URL and the REST API restrictions, because some themes and plugins rely on those endpoints. Enable them one at a time and check your site afterwards.
Rename or delete the open24-security folder in /wp-content/plugins/ over FTP or your hosting file manager. The plugin will be deactivated and wp-login.php will work again.
Yes. The WooCommerce options only appear when WooCommerce is active.
No. The only outbound request is to the official WordPress.org key generator API, and only when you choose to log out all users.
Under Login, set “Visitor IP read from” to the header your proxy sets. The screen shows the IP the plugin currently sees for you, so you can confirm the setting is right. Leave it on the direct connection unless there really is a proxy in front of the site: those headers are sent by the client, so trusting them without a proxy lets an attacker send a different IP on every login attempt and never get locked out.
Because that is where WordPress stores the security keys and salts, as PHP constants. Changing them is what invalidates every session cookie. See the Description for details on how the file is written safely.
Plugin details
Tags on WordPress.org
