Description
Ultimate Security handles the traffic that actually reaches a WordPress site: automated login attempts, brute-force runs, comment and form spam, and probes at well-known paths. It covers two-factor authentication, login lockouts, CAPTCHA, a movable login URL, session controls, vulnerability scanning, and Cloudflare edge rules — set up from one admin screen, without editing files or writing firewall rules by hand.
There is no usage tracking and nothing phones home. The plugin contacts an outside service only when you switch on a feature that needs one, and each is listed under External Services below. Features that belong to the Pro add-on are labelled as such.
Setup wizard
The first run is a five-step wizard. You answer a few questions about the site, it runs a quick scan, and you pick one of seven starting templates: basic, moderate, strict, agency, blog, membership, or WooCommerce. Before it changes anything it shows you a full diff, and you can undo everything it did later without losing edits you made yourself. It also gives you an emergency access link — keep it somewhere safe, and you can switch the plugin off from a browser if you ever lock yourself out.
Two-factor authentication
- Email one-time codes, no app required, for any user.
- Authenticator apps (TOTP and HOTP) with QR enrolment — Google Authenticator, Authy, Microsoft Authenticator and similar.
- Per-role configuration: pick which roles use email codes and which use an app.
- Rate limiting on code entry, with a configurable attempt limit and lockout.
- Optional 2FA event logging.
- Covers the WordPress, WooCommerce and Ultimate Member login forms, with a separate setting for XML-RPC.
Login access control
- Move
wp-login.phpto a secret URL so bots can’t find it, with a configurable post-login redirect. - HTTP Basic Authentication in front of
wp-login.phpandwp-admin, no.htaccessediting. The password is stored hashed, repeated failures trigger a lockout, and you can let trusted IPs through. - Show your own consent or policy text on the login form.
Password policies
- Require a minimum length, mixed case, numbers and special characters, or start from a preset.
- Expiry with advance warning, a grace period, and email notification.
- Password history, so old passwords can’t be reused.
- Force a password change on first login.
- Reject compromised passwords, checked against the Have I Been Pwned range API by k-anonymity — the password itself never leaves the site.
- Optionally turn off self-service password reset and point people at your own process instead.
Brute-force protection
- Limit failed logins and lock offenders out automatically.
- Progressive lockouts, so repeat offenders wait longer each time.
- Configurable retry-reset window, plus a permanent block list.
- A one-time recovery link, so a lockout doesn’t strand you.
Session management
- Limit concurrent logins per user; block the new login or end the oldest session.
- Idle timeout for inactive sessions.
- HttpOnly, Secure and SameSite flags on auth cookies.
- Optionally bind a session to its IP and/or browser to catch hijacking.
CAPTCHA and spam
- Google reCAPTCHA v2 and v3, with a v3 score threshold, IP and user-agent allowlists, a bypass for logged-in users, and a verification log.
- Cloudflare Turnstile, with theme, size, language and appearance options, deferred loading, custom failure messages, and its own log.
- Both cover the WordPress login, registration, lost-password and comment forms, and the WooCommerce login, registration, lost-password and checkout forms.
- No-conflict mode and provider priority keep two CAPTCHAs off the same form.
- Validate your site and secret keys from the settings page before going live.
- If the provider is unreachable, forms keep working.
Vulnerability scanning
- Scans WordPress core, plugins and themes for known vulnerabilities.
- No API key needed — it uses the keyless WPVulnerability database by default.
- Add a WPScan or Patchstack key for more coverage, with automatic failover between providers.
- Scheduled scans and email alerts, filtered by severity.
- Flags plugins that haven’t been updated in a long time.
- Scan history, run-to-run comparison, and an ignore list for findings you’ve accepted.
- Results show up in Site Health, the dashboard widget, the plugins list, and menu counters.
Cloudflare WAF rules
Connect your own Cloudflare account and manage edge rules from wp-admin.
- Let verified search, monitoring, backup, SEO and social crawlers through.
- Block aggressive crawlers and sensitive WordPress paths.
- Block data-center hosts and TOR exit nodes.
- Challenge large cloud providers and specific countries.
- Challenge VPN traffic and requests to
wp-login.php. - Virtual patches that block requests exploiting known core CVEs at the edge until you can update.
- Preview the generated expressions before deploying, review the live rules on your zone, and read request, threat and bandwidth analytics.
Security keys (salts)
- Rotate the keys and salts in
wp-config.phpon demand or on a schedule — daily, weekly, monthly, quarterly, or twice a year. - Advance notice before a scheduled rotation, so the forced re-login isn’t a surprise.
- Quiet hours, plus pause and skip-next controls.
- Rotation history, with the option to restore a previous set.
Update manager
- Set auto-update policy for core, plugins and themes, with per-plugin and per-theme overrides.
- Update windows, allowed days, and freeze periods for when you don’t want changes.
- Delay updates by a set number of days to let others hit the bugs first.
- Optional maintenance mode during updates, and detection of version-controlled installs.
- Email notifications and a daily digest.
Monitoring, security score and logs
- A security score with a per-check breakdown of what’s pulling it down.
- Activity log for logins, logouts, lockouts, and 2FA and password events, with a retention period you set.
- Session log for session events and anomalies.
- A “who’s online” view of currently active users.
- Core file-integrity check against the official WordPress.org checksums.
- Site Health entries covering plugin, server, database, filesystem, theme and WordPress diagnostics.
- A dashboard widget summarising failed logins, issues found, outdated plugins and the current score.
Test mode
Run your rules without blocking anyone and review a log of what would have been blocked before you enforce it. Choose which roles it applies to, keep admins excluded, and an admin-bar marker plus a dashboard notice remind you it’s on.
Tools, migration and backup
- Import from Wordfence Login Security — preview what comes across, run it, and roll it back if you change your mind.
- Export and import settings as JSON for staging-to-production moves or recovery.
- Reset all settings to defaults, and clear the plugin cache.
- Diagnostics for REST API, cron (with a manual run trigger), and server status.
- An emergency deactivation URL that switches the plugin off if you’re locked out.
Works with what you already run
Ultimate Security detects and adapts to WooCommerce, Ultimate Member, common page builders, form plugins, caching plugins and SEO plugins, and warns you when another security plugin is already doing the same job.
WP-CLI
wp ultimate-security template list
wp ultimate-security template apply <template> [--dry-run]
wp ultimate-security template undo
wp ultimate-security export [--file=<path>]
wp ultimate-security import <file> [--dry-run]
wp ultimate-security status
Learn more
- Website — features and articles.
- Documentation — setup guides, troubleshooting and how-tos.
- YouTube — walkthroughs and tutorials.
External Services
This plugin connects to the following third-party services, and only when you use the related feature:
Google reCAPTCHA
- When: reCAPTCHA protection is enabled. The reCAPTCHA script is then loaded in your visitors’ browsers on the protected forms.
- Data sent: the visitor’s reCAPTCHA response token, your site secret key, and the visitor’s IP address for verification.
- Endpoints: https://www.google.com/recaptcha/api.js (browser script, with a preconnect to https://www.gstatic.com) and https://www.google.com/recaptcha/api/siteverify (server-side verification).
- Terms: https://policies.google.com/terms — Privacy: https://policies.google.com/privacy
Cloudflare Turnstile
- When: Cloudflare Turnstile protection is enabled. The Turnstile script is then loaded in your visitors’ browsers on the protected forms.
- Data sent: the visitor’s Turnstile response token, your site secret key, and the visitor’s IP address for verification.
- Endpoints: https://challenges.cloudflare.com/turnstile/v0/api.js (browser script) and https://challenges.cloudflare.com/turnstile/v0/siteverify (server-side verification).
- Terms: https://www.cloudflare.com/website-terms/ — Privacy: https://www.cloudflare.com/privacypolicy/
WPVulnerability
- When: the Vulnerability Scanner runs. This is the default vulnerability database and requires no API key.
- Data sent: your WordPress version and the slugs of your installed plugins and themes.
- Endpoint: https://www.wpvulnerability.net/
- Privacy: https://www.wpvulnerability.net/
WPScan
- When: the Vulnerability Scanner runs and you have configured a WPScan API key.
- Data sent: your WPScan API key, your WordPress version, and the slugs of your installed plugins and themes.
- Endpoint: https://wpscan.com/api/v3/
- Terms: https://wpscan.com/terms-of-service/ — Privacy: https://wpscan.com/privacy-policy/
Patchstack
- When: the Vulnerability Scanner runs and you have configured a Patchstack API key.
- Data sent: your Patchstack API key, your WordPress version, and the slugs of your installed plugins and themes.
- Endpoint: https://patchstack.com/database/api/v2/
- Terms: https://patchstack.com/terms-of-service/ — Privacy: https://patchstack.com/privacy-policy/
WordPress.org Plugin and Theme Information API
- When: the Vulnerability Scanner checks whether an extension has been abandoned, and when the Update Manager gathers update information.
- Data sent: the slugs of your installed plugins and themes (no user data).
- Endpoints: https://api.wordpress.org/plugins/info/1.2/ and https://api.wordpress.org/themes/info/1.2/
- Privacy: https://wordpress.org/about/privacy/
WordPress.org Core Version Check
- When: the Update Manager checks for available WordPress core updates.
- Data sent: a standard WordPress core version-check request (no user data).
- Endpoint: https://api.wordpress.org/core/version-check/1.7/
- Privacy: https://wordpress.org/about/privacy/
WordPress.org Core Checksums
- When: you run the WordPress core file-integrity check.
- Data sent: your WordPress version and locale, in order to retrieve the official file checksums for comparison.
- Endpoint: https://api.wordpress.org/core/checksums/1.0/
- Privacy: https://wordpress.org/about/privacy/
WordPress.org Secret-Key (Salt) API
- When: you rotate WordPress security keys and salts, on demand or on a schedule.
- Data sent: a request for randomly generated salt strings (no site or user data).
- Endpoint: https://api.wordpress.org/secret-key/1.1/salt/
- Privacy: https://wordpress.org/about/privacy/
Cloudflare API
- When: you connect Cloudflare or preview, deploy, remove or analyse WAF rules.
- Data sent: your Cloudflare credentials or API token, the selected zone and rule data, and the API requests needed for verification, deployment and analytics.
- Endpoint: https://api.cloudflare.com/client/v4/
- Terms: https://www.cloudflare.com/website-terms/ — Privacy: https://www.cloudflare.com/privacypolicy/
Have I Been Pwned (Pwned Passwords)
- When: the “refuse compromised passwords” password-policy option is enabled and a password is set or changed.
- Data sent: the first 5 characters of the SHA-1 hash of the password (a k-anonymity range query). The password itself is never sent.
- Endpoint: https://api.pwnedpasswords.com/range/
- Privacy: https://haveibeenpwned.com/Privacy
Feedback and support email
- When: only when an administrator explicitly submits contact, migration, or deactivation feedback. Choosing “Skip & Deactivate” sends nothing.
- Data sent: the submitted message or deactivation reason and optional notes. Contact and migration requests also include diagnostic details shown with the form, such as the site URL, WordPress/PHP versions, active theme and plugin count, administrator profile, IP address, user agent, and referrer.
- Destination: support@wpultimatesecurity.com, delivered through the site’s configured WordPress email service.
- Privacy: https://www.wpultimatesecurity.com/privacy-policy/
Screenshots












Installation
Requirements: WordPress 5.6+ and PHP 7.0+. HTTPS is strongly recommended for 2FA and secure sessions.
📘 Full setup walkthrough: Documentation · Video tutorials
Install from your dashboard
- In WordPress, go to Plugins Add New and search for “wpultimatesecurity”.
- Click Install Now, then Activate.
- Follow the Security Wizard that appears — it scans your site, recommends settings, and shows you every change before applying it.
Install manually
- Download the plugin ZIP.
- Go to Plugins Add New Upload Plugin, choose the ZIP, and click Install Now.
- Click Activate, then follow the Security Wizard.
Or with WP-CLI: wp plugin install ultimate-security --activate
Recommended first 5 minutes
- Run the Security Wizard and apply a template that matches your site.
- Enable 2FA for all administrator accounts.
- Set login attempt limits and a lockout duration.
- Add CAPTCHA (reCAPTCHA or Cloudflare Turnstile) to your login, registration and comment forms.
- Set a custom login URL, save it somewhere safe, and store the emergency access link the wizard showed you.
- Run a vulnerability scan, then review the Security Score and Site Health before enabling stricter rules.
FAQ
-
Will this slow down my site?
-
It is built to stay lightweight — security checks run on login and form submission, not on every page view. Vulnerability scans run on a schedule in the background, not during visitor requests.
-
Do I need any technical or coding knowledge?
-
No. The setup wizard scans your site, recommends settings, and shows you every change before it is applied — and you can undo all of it. Every setting is in plain English.
-
I enabled 2FA or a custom login URL and locked myself out. How do I get back in?
-
Use the emergency deactivation URL the setup wizard showed you — open it in a browser and the plugin switches itself off. If you did not save it, deactivate the plugin manually: over FTP/SFTP rename the folder
/wp-content/plugins/ultimate-security, or over SSH runwp plugin deactivate ultimate-security. Then log in and reconfigure. -
Turnstile is blocking every login (for example after changing my security keys). How do I recover?
-
Add
define( 'ULTIMATE_SECURITY_DISABLE_TURNSTILE', true );towp-config.php. This fully disables Turnstile rendering and verification so you can log in. Then re-enter your Turnstile Site Key and Secret Key in the plugin settings (rotating WordPress security keys/salts makes previously saved keys unreadable — Site Health and an admin notice will tell you when this has happened) and remove the constant. The constant requires server access, so it is never a public bypass. -
Do I need an API key for vulnerability scanning?
-
No. The scanner works out of the box using the keyless WPVulnerability database. WPScan and Patchstack API keys are optional and only add extra coverage.
-
Does it work with WooCommerce?
-
Yes. Both reCAPTCHA and Cloudflare Turnstile can protect WooCommerce login, registration, lost-password and checkout forms, and there is a WooCommerce setup template in the wizard.
-
Do I need a Cloudflare account to use this plugin?
-
Only for the WAF Rules section. Those rules are deployed to your own Cloudflare zone, so they need a Cloudflare account and an API token. Every other feature works without one.
-
Does it work with a persistent object cache (Redis, Memcached)?
-
Yes. Login lockouts, two-factor sign-in sessions and similar short-lived state are stored as WordPress transients, so with a persistent object cache they live in that cache instead of the database. Give the cache enough memory that it does not evict entries early, or a lockout can end sooner than configured.
-
Does it work on WordPress Multisite?
-
The plugin activates and runs on Multisite, and its uninstall routine is network-aware. It has not been tested as extensively on Multisite as on single-site installs, so validate on a staging network first and configure settings per site.
-
Does the custom login URL work with caching and CDNs?
-
Yes. Exclude the login path from full-page caching (most caching plugins do this for login and admin pages automatically) so the secret URL is never served from cache.
-
Will it conflict with other security or CAPTCHA plugins?
-
It can if two plugins do the same job. Pick one plugin per function (one 2FA, one CAPTCHA, one login limiter) and disable the overlapping feature in the other. Ultimate Security detects common security plugins and warns you.
-
I already use another security plugin. Can I bring my settings across?
-
Settings can be imported from Wordfence Login Security. You get a preview of exactly what will be imported before anything is applied, and you can roll the import back afterwards.
-
Does the plugin track me or phone home?
-
No. Ultimate Security does not collect product-usage telemetry. It contacts third-party services only when you use a feature that requires one, and every one of those is listed under External Services below.
-
What does the plugin store about my visitors?
-
IP addresses and user agents are recorded in the activity and session logs so you can investigate login attempts, with a retention period you control (30 days by default). Test Mode keeps its own log of what would have been blocked. “Who’s online” rows expire after 60 seconds. Nothing is sent off your site except through the services listed below.
-
Is it GDPR-friendly?
-
The plugin is self-hosted and stores its data in your own database. Outbound calls are limited to the feature-specific services listed under External Services, such as reCAPTCHA, Turnstile, the vulnerability databases and WordPress.org APIs.
-
What happens to my data when I uninstall?
-
By default the plugin leaves its data in place. If you enable the “delete plugin data” option in the plugin’s advanced settings before uninstalling, its database tables, options and user meta are removed on uninstall.
-
What is the difference between Free and Pro?
-
Everything described on this page is in the free plugin: the setup wizard, email and app-based 2FA, brute-force lockout, custom login URL, HTTP Basic Auth, password policies, session management, reCAPTCHA and Turnstile, vulnerability scanning, Cloudflare WAF rules, security-key rotation (on demand and scheduled), the Update Manager, Security Score, activity logs, core file-integrity checking, Site Health, Test Mode, Wordfence migration, and settings backup and restore. Ultimate Security Pro is a separate add-on that requires this free plugin and adds further authentication, monitoring, automation and maintenance features not included here.
-
How do I get support?
-
Use the plugin support forum on WordPress.org, or visit https://www.wpultimatesecurity.com.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Ultimate Security – Vulnerability Scanner, 2FA, and Login Protection” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “Ultimate Security – Vulnerability Scanner, 2FA, and Login Protection” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.26
- Fix: The session activity list and the failed sign-in count on the WordPress dashboard now update as soon as something happens, instead of lagging behind by up to an hour.
- Fix: The failed sign-in count on the dashboard shows real numbers again. It was reading a table that no longer exists and always showed zero.
- Fix: Cloudflare Turnstile no longer breaks the page when a challenge does not match the form it came from, when Cloudflare cannot be reached, or when its keys cannot be read.
- Fix: The WordPress core file check now explains itself when it cannot reach WordPress.org, instead of failing with a PHP error.
- Fix: Cached scan results are cleared properly on sites that use Redis or Memcached object caching, a cached dashboard status that could get stuck is refreshed, and uninstalling now removes the last of the plugin’s temporary data.
- Performance: Security logs are cleaned up automatically after 90 days, so the log tables no longer grow without limit. The clean-up runs in small batches, and developers can change the retention period with a filter.
- Performance: Searching session activity is faster, and it loads faster on sites with a long history.
- Performance: Who’s Online no longer does any work for logged-out visitors, so ordinary page views are unaffected by it.
- Performance: User and session lists load faster on sites with many users, and Test Mode records simulated blocks with less database work.
- Performance: The lockout clean-up job runs hourly instead of every minute. Lockouts still end exactly when they are supposed to.
- Improvement: The plugin now runs on MariaDB and on SQLite-based setups such as WordPress Playground and Local Studio, in addition to MySQL.
- Improvement: Settings menus list free features first and Pro features last, and the header Scans menu marks Pro scanners.
- Docs: A new FAQ entry explains how object caching (Redis, Memcached) affects login lockouts and two-factor sign-in sessions.
- Docs: The plugin listing now has captions for its screenshots.
1.0.25
- Fixed: Session cookie hardening (SameSite, Secure) was overridden by WordPress core and never applied.
- Fixed: Dashboard hijack and idle-timeout counters read the wrong table and always showed 0.
- Fixed: Ending a session from Active Sessions could fail with a fatal error instead of a clear message.
- Fixed: Header search listed Active Sessions as Pro and Session Automations as free.
- Security: Ending a session from Active Sessions is now a POST request and is recorded in the activity log.
- Performance: Active Sessions only queries users who actually hold a session.
- Improvement: Settings menus list free features first and Pro features last, and the header Scans menu marks Pro scanners.
1.0.24
- New: The redesigned admin interface is now the default for everyone — a cleaner dashboard, settings, and reporting, with light and dark modes that follow your system preference.
- Fix: Scheduled security-key (salt) rotation is a free feature, but the setup wizard displayed it as Pro and the Maximum Security template withheld its settings from free installs. Both corrected — applying that template now enables scheduled rotation.
- Fix: Security headers and XML-RPC protection are Pro features and are no longer labelled as free in the setup wizard.
- Docs: The readme now documents the complete free feature set and discloses every third-party service the plugin contacts.
- Maintenance: Removed unreachable code — an unused salt-change extension, a duplicate session route registrar, an unscheduled cron entry, an unused settings group, and unused Pro-feature permission helpers.
- Fix: The maintenance file written during plugin and theme updates was not valid PHP. On sites using that option it printed stray text at the top of every page, which broke logins and the plugin’s own admin screens, and it could be left behind if an update failed part way through. Maintenance mode itself never actually engaged.
- Fix: Changing your security keys and salts now verifies the new wp-config.php before replacing the old one. Previously a bad network response could be written into the file, leaving the site unable to start.
- Fix: Saved API keys (reCAPTCHA, Turnstile, WPScan, Patchstack, Twilio) survive a key and salt change. They were previously left unreadable, so those integrations stopped working with no explanation.
- Fix: Turning off automatic updates no longer stops WordPress from checking for updates or slows down the admin area. Update notices, including security releases, keep working.
- Security: The two-factor code screen is now tied to the browser that signed in. It could previously be shown to another visitor who requested the login page at the right moment.
- Security: Two-factor authentication is now required over XML-RPC and for application passwords, which previously bypassed it.
- Security: Login attempt limits now count by IP address as well as username, so attempts spread across many usernames are limited and one account can no longer be locked out on demand. Lockout messages no longer reveal whether an account exists.
- Security: CAPTCHA can no longer be skipped by sending an authorization header with the login request.
- Security: The plugin deactivation link is now confirmed with a form submission instead of acting on a plain link, its secret is kept encrypted, and it changes after each use.
- Security: The compromised-password check is rate limited. It could previously be called repeatedly by anyone to exhaust the server.
- Security: HTTP authentication now also covers xmlrpc.php, and no longer alters the submitted password before checking it, which could reject valid passwords.
- Security: The login recovery link is kept out of settings exports and support reports, and credentials are removed on uninstall even when settings are kept.
- Performance: Scan results and CAPTCHA debug logs are no longer loaded on every page request, and settings are read later in the load order.
- Performance: Front-end assets now load only where a plugin feature is actually on the page — a page with no forms, widgets, or CAPTCHA loads no plugin CSS/JS and no jQuery.
- Improvement: Reworked the Vulnerability Scanner scan-history view — full-width results table and a corrected trend chart.
- Maintenance: Removed the previous interface and its opt-in switch, the now-unused styles behind it, and dead IP-switch AJAX handlers.
1.0.23
- Privacy: Removed unpublished product-usage analytics code and dependencies before release.
- Privacy: Removed automatic dashboard blog-feed and remote country-flag requests.
- Fix: Free mode no longer requests Pro-only blocklist routes or mounts Pro-only settings screens.
- Compatibility: Restored the documented WordPress 5.6 and PHP 7.0 runtime floor without changing the database schema.
- Maintenance: Removed repository GitHub Actions while preserving local release checks.
1.0.22
- Improvement: Added localized passkey login feedback supplied by Ultimate Security Pro.
- Security: Render passkey login errors as text instead of interpolating error content into HTML.
1.0.21
- New: WordPress Salt keys rotation option. Now you can schedule, skip and more when rotating keys.
- New: Now you can see the reCaptcha Logs directly from the plugin’s setting page.
- Improvement: Both reCaptcha and Cloudflare Turnstile follow a similar settings structure for consistency.
- Fix: Cloudflare Turnstile and reCAPTCHA whitelist option was not working properly.
1.0.20
- New: Improved Session Management settings including concurrent login limits, session cookie hardening and more,
- New: Cloudflare Turnstile and reCAPTCHA CAPTCHA verifcation when applying their respective keys.
- Improvement: Cloudflare WAF rules function improvement.
- Improvement: Code optimization and performance improvements.
1.0.19
- Fix: 2FA User role was not working properly.
- Fix: Login activity dashboard modal was showing wrong agent.
- Improvement: Better user friendly Server Protection Card Design
- Improvement: Code cleanup and optimization.
1.0.18
- New: One-click Cloudflare WAF rules apply
- New: New Modal for Login activity with detailed information.
- Improvement: Code cleanup and optimization
- Fix: Login redirected URL was showing exisiting login for password reset
1.0.17
- Fix: Minor bug fixes and stability improvements
- Improvement: Code cleanup and optimization
1.0.16
- Improvement: Code improvements to the ovearll plugin making it snappier.
1.0.15
- Improvement: Conflict management between applied settings.
- Improvement: UI improvements to existing settings pages. Making it more intuitive to use.
- Fix: Multiple bug fixes to dashboard. You should get more accurate results now.
- Fix: New deactivation URL was not saving after deactiviting-activating plugin.
1.0.14
- Fix: Email 2FA codes were not being sent properly
- Fix: 2FA code page flickering effect after login
1.0.13
- New: Completely redesigned user interface for better usability
1.0.12
- New: Security Score meter to track your site’s security level
- Improvement: Enhanced modal design for better UI/UX
1.0.11
- Fix: Minor UI bug fixes
1.0.10
- Security: Removed unauthenticated AJAX actions
- Security: REST routes now require admin permission
1.0.9
- Fix: Dashboard emergency deactivation URL display issue
1.0.8
- Improvement: Human-readable values in activity log
- Improvement: Reduced plugin size with optimized code
- Fix: 2FA reset issue for users
- Fix: Password policy not applying to new users
1.0.7
- New: Activity Log feature
- New: Improved dashboard design
- Fix: Nonce validation issues
- Fix: Turnstile not showing on comment forms
1.0.6
- Fix: Custom login setup issues
- Fix: Email 2FA asking for OTP twice
- Fix: Feedback form email delivery
- Improvement: Reorganized menu navigation
- Improvement: Performance optimizations
1.0.5
- Fix: Request logs page display issue
- Fix: URL Guard SQL query display
- Improvement: Performance optimizations
1.0.4
- Redesigned settings page interface
