This commit is contained in:
Javier Casares 2026-06-06 05:08:20 +00:00
commit 054060374e

View file

@ -4,7 +4,7 @@ Tags: security, two-factor authentication, login, otp
Requires at least: 6.4
Tested up to: 7.0
Requires PHP: 8.0
Stable tag: 1.4.0
Stable tag: 1.5.0
License: GPLv3 or later
License URI: https://www.gnu.org/licenses/gpl-3.0.html
@ -59,6 +59,22 @@ Yes. Activate the plugin at the network level. Network administrators can set an
== Changelog ==
= 1.5.0 =
_Release date: 2026-06-05_
**Added**
* Full audit user table — WP_List_Table with sortable columns (user, last verified), role and status filters, and one-click CSV export.
* GeoIP country restrictions — optional MaxMind GeoLite2 integration: per-country allow list (bypass 2FA), deny list (block login), always-challenge list (override frequency). Disabled when no database file is configured.
* Require 2FA before creating Application Passwords — REST endpoint rejects requests unless 2FA was completed within the last 15 minutes (configurable via `robotstxt_2fa_app_password_verification_window` filter).
* WP-CLI `wp 2fa export` — outputs a full CSV report.
* New developer filter `robotstxt_2fa_force_challenge` — override frequency-based skip and always require a fresh challenge.
**Fixed**
* Email digest cron now correctly reschedules when the frequency is changed between weekly and monthly.
= 1.4.0 =
_Release date: 2026-06-05_
@ -93,22 +109,6 @@ _Release date: 2026-06-05_
* `wp 2fa bypass <user_id> [--days=<n>]` — grant a temporary bypass for a locked-out user.
* WP-CLI commands are only loaded when the `WP_CLI` constant is defined and truthy.
= 1.2.1 =
_Release date: 2026-06-05_
**Fixed**
* Recovery code confirmation without checking the method checkbox now correctly activates the method and enables 2FA.
* Fatal error on admin profile pages in multisite — `maybe_handle_frontend_save()` now returns early when `is_admin()` is true.
* OTP and recovery confirmation text inputs were disabled by JS when the Enable toggle was off, preventing values from reaching the server.
* "Regenerate codes" now removes recovery codes from active methods and requires re-confirmation before reactivating.
* Entering a valid OTP code or recovery confirmation code activates the method even without checking the Enable checkbox.
**Security**
* `RECOVERY_REGENERATE_FIELD` POST value now validated with strict `=== '1'` check.
= Previous versions =
For the full changelog see the [changelog.txt](https://git.robotstxt.es/ROBOTSTXT/robotstxt-2fa/raw/branch/main/changelog.txt) file.