外掛說明

The Two-Factor plugin adds an extra layer of security to your WordPress login by requiring users to provide a second form of authentication in addition to their password. This helps protect against unauthorized access even if passwords are compromised.

設定說明

Important: Each user must individually configure their two-factor authentication settings.

個人使用者

Navigate to your profile: Go to “Users” “Your Profile” in the WordPress admin
Find Two-Factor Options: Scroll down to the “Two-Factor Options” section
Choose your methods: Enable one or more authentication providers (noting a site admin may have hidden one or more so what is available could vary):
- Authenticator App (TOTP) – Use apps like Google Authenticator, Authy, or 1Password
- 透過電子郵件傳送驗證碼 – Receive one-time codes via email
- Backup Codes – Generate one-time backup codes for emergencies
- 測試模式 – For testing purposes only (requires WP_DEBUG)
Configure each method: Follow the setup instructions for each enabled provider
Set primary method: Choose which method to use as your default authentication
Save changes: Click “Update Profile” to save your settings

網站管理員

Plugin settings: The plugin provides a settings page under “Settings Two-Factor” to configure which providers should be disabled site-wide.
User management: Administrators can configure 2FA for other users by editing their profiles
Security recommendations: Encourage users to enable backup methods to prevent account lockouts

可用的驗證方法

驗證碼產生器 App (TOTP) – 建議使用

Security: High – Time-based one-time passwords
Setup: Scan QR code with authenticator app
Compatibility: Works with Google Authenticator, Authy, 1Password, and other TOTP apps
Best for: Most users, provides excellent security with good usability

備用驗證碼 – 建議使用

Security: Medium – One-time use codes
Setup: Generate 10 backup codes for emergency access
Compatibility: Works everywhere, no special hardware needed
Best for: Emergency access when other methods are unavailable

透過電子郵件傳送驗證碼

Security: Medium – One-time codes sent via email
Setup: Automatic – uses your WordPress email address
Compatibility: Works with any email-capable device
Best for: Users who prefer email-based authentication

FIDO U2F 安全金鑰

Deprecated and removed due to loss of browser support.

測試模式

Security: None – Always succeeds
Setup: Only available when WP_DEBUG is enabled
Purpose: Testing and development only
Best for: Developers testing the plugin

重要注意事項

HTTPS 要求

All methods work on both HTTP and HTTPS sites

瀏覽器相容性

TOTP and email methods work on all devices and browsers

帳號復原

Always enable backup codes to prevent being locked out of your account
If you lose access to all authentication methods, contact your site administrator

安全性最佳做法

Use multiple authentication methods when possible
Keep backup codes in a secure location
Regularly review and update your authentication settings

For more information about two-factor authentication in WordPress, see the WordPress Advanced Administration Security Guide.

如需進一步了解這個外掛的開發沿革，請參閱這篇文章。

動作及篩選器

以下所列為這個外掛提供的動作及篩選器勾點：

two_factor_providers 篩選器：這個篩選器會覆寫如電子郵件及 TOTP 等兩步驟驗證方式。陣列值為兩步驟驗證方式的 PHP 類別名稱。
two_factor_providers_for_user 篩選器：這個篩選器會覆寫已為特定使用者啟用的兩步驟驗證方式。陣列值的第一個引數是驗證方式類別的執行個體，第二個引數為使用者物件 WP_User。
two_factor_enabled_providers_for_user 篩選器：這個篩選器會覆寫已為使用者啟用的兩步驟驗證方式清單。第一個引數是已啟用的功能提供程式類別名稱值陣列，第二個引數為使用者 ID。
two_factor_is_required_for_user filter controls whether two-factor authentication is required for a user. Return false to bypass the two-factor flow (e.g. for trusted IP addresses). First argument is a boolean (whether the user has a primary provider configured), the second argument is the WP_User object.
two_factor_fallback_provider_for_user filter overrides the provider forced on when none of a user’s stored two-factor providers are still registered (e.g. after a provider plugin is deactivated). Defaults to Two_Factor_Email. First argument is the provider classname, the second is the user ID, the third is the array of provider classnames that were stored for the user but are no longer registered. The returned provider must be registered and available to the user (is_available_for_user()), or the user is shown an error instead of being let through with a fallback.
two_factor_user_authenticated 動作：這個動作會接收已登入的 WP_User 物件作為第一個引數，用於完成驗證工作流程後立即確定已登入的使用者。
two_factor_user_api_login_enable 篩選器：這個篩選器會限制 REST API 及 XML-RPC 僅能使用應用程式密碼，第二個引數為使用者 ID。
two_factor_email_token_ttl 篩選器：這個篩選器會覆寫電子郵件權杖產生後的使用期限 (以秒為單位)。接受第一個引數為以秒為單位的時間間隔設定後，才能驗證 WP_User 物件的 ID。
two_factor_email_token_length 篩選器：這個篩選器會覆寫電子郵件權杖預設為 8 個字元的設定。
two_factor_backup_code_length 篩選器：這個篩選器會覆寫備用代碼預設為 8 個字元的設定，提供與 WP_User 關聯的使用者作為第二個引數。
two_factor_rest_api_can_edit_user 篩選器：這個篩選器會使用 REST API 覆寫使用者的 Two-Factor 外掛設定。第一個引數是目前的 $can_edit 布林值，第二個引數為使用者 ID。
two_factor_before_authentication_prompt 動作：這個動作會接收提供者物件及並在驗證輸入表單顯示提示前觸發。
two_factor_after_authentication_prompt 動作：這個動作會接收提供者物件及並在驗證輸入表單顯示提示後觸發。
two_factor_after_authentication_input 動作：這個動作會接收提供者物件及並在驗證輸入表單輸入相關資料後觸發；如果表單中沒有任何輸入任何相關資料，這個動作會在 two_factor_after_authentication_prompt 後立即觸發。
two_factor_login_backup_links filters the backup links displayed on the two-factor login form.
two_factor_login_nonce_failed action which fires when a login nonce fails verification. Provides the ID of the user the nonce was presented for as the first argument, and the reason as the second: no_nonce_stored, expired, or mismatch.
two_factor_log_login_nonce_failures filter overrides whether a failed login nonce verification is written to the PHP error log. Defaults to true for expired and mismatch, and false for no_nonce_stored, which any unauthenticated request can reach. Provides the user ID as the second argument and the reason as the third.

WP-CLI Commands

The plugin includes a wp two-factor WP-CLI namespace for managing two-factor authentication from the command line. All commands accept a user by ID, login, or email.

wp two-factor status <user> — Shows a user’s current 2FA status (read-only). Supports --format=json.
wp two-factor list-providers — Lists all registered two-factor providers.
wp two-factor enable <user> <provider> — Enables a provider for a user. Providers that require a shared secret (like TOTP) can’t be enabled this way and will point you to the profile page instead.
wp two-factor disable <user> [<provider>] — Disables a single provider, or performs a full reset of all 2FA for the user when no provider is given. Both forms prompt for confirmation unless --yes is passed.
wp two-factor backup-codes generate <user> [--count=<n>] — Generates a fresh set of backup codes for a user, replacing any existing ones. Defaults to 10 codes.
wp two-factor unlock <user> — Clears a user’s login rate-limit/throttle without changing their 2FA configuration.

Run wp help two-factor for the full list, or wp help two-factor <command> for options and examples for a specific command.

Redirect After the Two-Factor Challenge

To redirect users to a specific URL after completing the two-factor challenge, use WordPress Core built-in login_redirect filter. The filter works the same way as in a standard WordPress login flow:

add_filter( 'login_redirect', function( $redirect_to, $requested_redirect_to, $user ) {
    return home_url( '/dashboard/' );
}, 10, 3 );

螢幕擷圖

登入 WordPress 後，使用電子郵件傳送驗證碼進行驗證：在登入期間顯示電子郵件驗證畫面 — Two-factor options under User Profile – Shows the main configuration area where users can enable different authentication methods.

常見問題集

Two-Factor 外掛支援哪些 PHP 及 WordPress 版本？

這個外掛支援 WordPress 最新的 2 個主要版本及這些 WordPress 核心程式所支援的 PHP 最低版本需求。

如何針對程式碼錯誤進行意見反應或取得協助？

Two Factor 的 GitHub 待解問題頁面，是回報外掛程式碼錯誤、功能建議及任何 (非安全性相關) 意見反應的最佳集中地。在提交新問題前，請先搜尋現有待解問題中，是否已有其他人回報過類似的問題。

在何處可以回報安全性程式碼錯誤？

外掛參與者及 WordPress 社群對安全性程式碼錯誤一向嚴陣以待，我們非常感謝使用者披露相關發現所付出的心力，並會盡全力解決使用者提出的問題。

如需回報安全性問題，請參考 WordPress HackerOne 計畫。

What if I lose access to all my authentication methods?

If you have backup codes enabled, you can use one of those to regain access. If you don’t have backup codes or have used them all, you’ll need to contact your site administrator to reset your account. This is why it’s important to always enable backup codes and keep them in a secure location.

Can I use this plugin with WebAuthn?

The plugin previously supported FIDO U2F, which was a predecessor to WebAuthn. There is an open issue to add WebAuthn support here.

Is there a recommended way to use passkeys or hardware security keys with Two-Factor?

Yes. For passkeys and hardware security keys, you can install the Two-Factor Provider: WebAuthn plugin. It integrates directly with Two-Factor and adds WebAuthn-based authentication as an additional two-factor option for users.

Does this plugin work on WordPress Multisite?

Yes. The Two-Factor plugin is compatible with WordPress Multisite. Each user configures their own 2FA settings via their profile, and because authentication codes are stored in WordPress user meta, the configuration is tied to the user account and valid across all sites in the network. However, there are no network-wide settings — a super admin cannot enforce or configure 2FA globally from the Network Admin dashboard. To manage 2FA for a specific user, edit their profile on any site where they have an account.

How do I disable 2FA for a user who is locked out?

As an administrator, go to Users All Users in the WordPress admin, click Edit on the affected user’s profile, scroll down to the Two-Factor Options section, and uncheck all enabled methods, then click Update User. This will remove 2FA for that user, allowing them to log in with their password alone. You can also do this via WP-CLI with wp two-factor disable –yes, which performs a full reset (see the WP-CLI Commands section above). Once they’re back in, encourage them to re-enable 2FA and generate fresh backup codes.

Can I require 2FA for all users or specific roles?

Not through the plugin’s interface — there are no built-in enforcement settings. However, developers can use the two_factor_providers_for_user filter to control which providers are available per user or role, and combine it with custom logic to redirect users who haven’t set up 2FA. Native enforcement support is a known and tracked feature request — follow the discussion at GitHub issue #255.

使用者評論

jhonhorac 2026 年 6 月 14 日 1 則留言

It's an excellent plugin; I use it on all my sites.

vee 2026 年 6 月 10 日 1 則留言

The basic options expected:1. I must be able to use any authentication app.2. An option to use email as 2nd auth.But this plugin also have backup code.

kloproterra 2026 年 5 月 28 日 4 則留言

This plugin requires individual users to manage 2FA. Individual users can remove 2FA from their profile at any time leaving that account vulnerable. An admin would need to check regularly that this hasn't been removed. There is discussion about a custom function to force a user back to the profile page. I tested this. A user can still leave the account with 2FA off, albeit they cannot navigation anywhere but the profile page. However, in this state a bad actor can login with a password only to the unprotected account, then configure 2FA to their own device, this then removes the redirect and therefore undermines the entire process. This is a significant flaw. However, the plugin can protect a single admin account but any sort of user hierarchy is not protected.

bowerwebsolutions 2026 年 5 月 7 日 1 則留言

Not only did it work well for my use case with a customer who wanted to offer optional 2fa, but when i asked about customizing the code validation page i had a response in minutes. Very impressive. Worked well with a theme my login branded site.

aelbo 2026 年 4 月 27 日 1 則留言

Fonctionne parfaitement, simple et fiable

mjezegou35 2026 年 4 月 23 日 1 則留言

I am in version 6.6.2 of WordPress and in multisite network version. Is it possible to activate your plugin despite the constraint tested up to 6.9.1, please? I can't activate it at the network level?

閱讀全部 210 則使用者評論

參與者及開發者

以下人員參與了開源軟體〈Two Factor〉的開發相關工作。

〈Two Factor〉外掛目前已有 43 個本地化語言版本。感謝全部譯者為這個外掛做出的貢獻。

將〈Two Factor〉外掛本地化為台灣繁體中文版

對開發相關資訊感興趣？

任何人均可瀏覽程式碼、查看 SVN 存放庫，或透過 RSS 訂閱開發記錄。

變更記錄

0.17.0 – 2026-09-25

Security Fixes: Ensure that regular passwords can’t bypass the two-factor requirement for REST API and XML-RPC requests by @faisalahammad in #989. Thanks mqrble for responsibly reporting the issue.
Security Fixes: Add diagnostics for failed login nonce verification by @georgestephanis in #973. Thanks Ananda Dhakal (Patchstack) for responsibly reporting the issue.
New Features: Add WP-CLI support with wp two-factor commands by @masteradhoc in #905
New Features: Respect intentional bypass via the two_factor_is_required_for_user filter by @masteradhoc in #882
New Features: Add a two_factor_fallback_provider_for_user filter for when a user’s stored providers are no longer registered by @masteradhoc in #882
New Features: Add early notice for soon exhausting recovery codes by @masteradhoc in #907
New Features: Add privacy policy content registration by @masteradhoc in #869
Bug Fixes: Fail closed when CSPRNG is unavailable during nonce generation by @dknauss in #877
Bug Fixes: Only clear the login nonce once it has expired by @georgestephanis in #980
Bug Fixes: Fix unslashed REMOTE_ADDR warning in email provider by @masteradhoc in #975
Bug Fixes: Fix TOTP verify button after resetting authenticator app by @lakrisgubben in #979
Bug Fixes: Remove two_factor_enabled_providers option on uninstall by @faisalahammad in #903
Bug Fixes: Fix misleading notice by @masteradhoc in #858
Bug Fixes: Reword mixed-audience login failure notice to be informational by @dknauss in #922
Bug Fixes: Rework fail-safe by @masteradhoc in #927
Bug Fixes: Add coverage for provider-specific fallback notices by @dknauss in #923
Bug Fixes: Fix HTML5 validation issues by @masteradhoc in #910
Bug Fixes: Fix users list table fatals (wp_die) when a user’s 2FA provider is deregistered by @masteradhoc in #933
Development Updates: Prepare for the WordPress 7.0 release by @masteradhoc in #834
Development Updates: Prepare for the WordPress 7.1 release by @masteradhoc in #900
Development Updates: Sync login_header() and login_footer() with WP 7.1 by @masteradhoc in #963
Development Updates: Update PHPStan to 2.x and exclude includes/ from analysis by @masteradhoc in #972
Development Updates: Validate against PHPStan version 3, 4 and 5 by @masteradhoc in #948
Development Updates: Update wp-coding-standards/wpcs to 3.4.1 by @obenland in #947
Development Updates: Fix PHPCS and PHPStan issues across multiple files by @aslamdoctor in #818
Development Updates: Remove ReflectionProperty::setAccessible() and ReflectionMethod::setAccessible() calls in the test suite by @masteradhoc in #942
Development Updates: Fix Codecov badge by adding OIDC permission for tokenless upload by @nimesh-xecurify in #856
Development Updates: Update GitHub Actions workflows by @johnbillion in #892
Development Updates: Update Playground PR preview action to v4 by @obenland in #985
Development Updates: Add FAQ entries for Multisite, locked-out users, and role enforcement by @masteradhoc in #881
Development Updates: Update .md files with the latest two-factor changes and requirements by @masteradhoc in #929
Development Updates: Update PR template by @masteradhoc in #870
Development Updates: Unbreak CI: PHPStan false positive and matrix fail-fast by @georgestephanis in #974
Dependency Updates: Bump the qrcode-generator runtime dependency by @kasparsd
Dependency Updates: Bump qs and express by @dependabot[bot] in #895
Dependency Updates: Bump adm-zip and @wordpress/scripts by @dependabot[bot] in #988

0.16.0 – 2026-03-27

Breaking Changes: Remove legacy FIDO U2F provider support by #439.
New Features: Add a dedicated settings page for plugin configuration in wp-admin by #764.
New Features: Add a support links filter so consumers can customize contextual recovery/help links by #615.
New Features: Refresh backup codes UI styling and behavior by #804.
Bug Fixes: Delete stored TOTP secrets when the TOTP provider is disabled by #802.
Bug Fixes: Harden provider handling so login/settings checks do not fail open when expected providers disappear by #586.
Bug Fixes: Ensure only configured providers are saved and enabled in user settings by #798.
Bug Fixes: Improve settings-page accessibility and fix profile settings link behavior by #828 and #830.
Bug Fixes: Resolve PHPCS violations in provider files by #851.
Development Updates: Move login styles and provider scripts from inline output to enqueued/external assets by #807 and #814.
Development Updates: Improve inline docs and static-analysis compatibility (WPCS/phpstan) by #810, #815, and #817.
Development Updates: Improve unit test reliability and integrate CI code coverage reporting by #825, #841, and #842.
Development Updates: Update readme docs and modernize CI workflow infrastructure by #835, #837, #843, and #849.
Dependency Updates: Bump qs from 6.14.1 to 6.14.2 by #794.
Dependency Updates: Bump basic-ftp from 5.0.5 to 5.2.0 by #816.
Dependency Updates: Apply automatic lint/format updates and associated Composer package refreshes by #799.

0.15.0 – 2026-02-13

Breaking Changes: Trigger two-factor flow only when expected by @kasparsd in #660 and #793.
New Features: Include user IP address and contextual warning in two-factor code emails by @todeveni in #728
New Features: Optimize email text for TOTP by @masteradhoc in #789
New Features: Add “Settings” action link to plugin list for quick access to profile by @hardikRathi in #740
New Features: Additional form hooks by @eric-michel in #742
New Features: Full RFC6238 Compatibility by @ericmann in #656
New Features: Consistent user experience for TOTP setup by @kasparsd in #792
Documentation: @since docs by @masteradhoc in #781
Documentation: Update user and admin docs, prepare for more screenshots by @jeffpaul in #701
Documentation: Add changelog & credits, update release notes by @jeffpaul in #696
Documentation: Clear readme.txt by @masteradhoc in #785
Documentation: Add date and time information above TOTP setup instructions by @masteradhoc in #772
Documentation: Clarify TOTP setup instructions by @masteradhoc in #763
Documentation: Update RELEASING.md by @jeffpaul in #787
Development Updates: Pause deploys to SVN trunk for merges to master by @kasparsd in #738
Development Updates: Fix CI checks for PHP compatability by @kasparsd in #739
Development Updates: Fix Playground refs by @kasparsd in #744
Development Updates: Persist existing translations when introducing new helper text in emails by @kasparsd in #745
Development Updates: Fix missing_direct_file_access_protection by @masteradhoc in #760
Development Updates: Fix mismatched_plugin_name by @masteradhoc in #754
Development Updates: Introduce Props Bot workflow by @jeffpaul in #749
Development Updates: Plugin Check: Fix Missing $domain parameter by @masteradhoc in #753
Development Updates: Tests: Update to supported WP version 6.8 by @masteradhoc in #770
Development Updates: Fix PHP 8.5 deprecated message by @masteradhoc in #762
Development Updates: Exclude 7.2 and 7.3 checks against trunk by @masteradhoc in #769
Development Updates: Fix Plugin Check errors: MissingTranslatorsComment & MissingSingularPlaceholder by @masteradhoc in #758
Development Updates: Add PHP 8.5 tests for latest and trunk version of WP by @masteradhoc in #771
Development Updates: Add phpcs:ignore for falsepositives by @masteradhoc in #777
Development Updates: Fix(totp): otpauth link in QR code URL by @sjinks in #784
Development Updates: Update deploy.yml by @masteradhoc in #773
Development Updates: Update required WordPress Version by @masteradhoc in #765
Development Updates: Fix: ensure execution stops after redirects by @sjinks in #786
Development Updates: Fix WordPress.Security.EscapeOutput.OutputNotEscaped errors by @masteradhoc in #776
Dependency Updates: Bump qs and express by @dependabot[bot] in #746
Dependency Updates: Bump lodash from 4.17.21 to 4.17.23 by @dependabot[bot] in #750
Dependency Updates: Bump lodash-es from 4.17.21 to 4.17.23 by @dependabot[bot] in #748
Dependency Updates: Bump phpunit/phpunit from 8.5.44 to 8.5.52 by @dependabot[bot] in #755
Dependency Updates: Bump symfony/process from 5.4.47 to 5.4.51 by @dependabot[bot] in #756
Dependency Updates: Bump qs and body-parser by @dependabot[bot] in #782
Dependency Updates: Bump webpack from 5.101.3 to 5.105.0 by @dependabot[bot] in #780

0.14.2 – 2025-12-11

New Features: Add filter for rest_api_can_edit_user_and_update_two_factor_options by @gutobenn in #689
Development Updates: Remove Coveralls tooling and add inline coverage report by @kasparsd in #717
Development Updates: Update blueprint path to pull from main branch instead of a deleted f… by @georgestephanis in #719
Development Updates: Fix blueprint and wporg asset deploys by @kasparsd in #734
Development Updates: Upload release only on tag releases by @kasparsd in #735
Development Updates: Bump playwright and @playwright/test by @dependabot[bot] in #721
Development Updates: Bump tar-fs from 3.1.0 to 3.1.1 by @dependabot[bot] in #720
Development Updates: Bump node-forge from 1.3.1 to 1.3.2 by @dependabot[bot] in #724
Development Updates: Bump js-yaml by @dependabot[bot] in #725
Development Updates: Mark as tested with the latest WP core version by @kasparsd in #730

0.14.1 – 2025-09-05

Don’t URI encode the TOTP url for display. by @dd32 in #711
Removed the duplicate Security.md by @slvignesh05 in #712
Fixed linting issues by @sudar in #707
Update development dependencies and fix failing QR unit test by @kasparsd in #714
Trigger checkbox js change event by @gedeminas in #688

0.14.0 – 2025-07-03

Features: Enable Application Passwords for REST API and XML-RPC authentication (by default) by @joostdekeijzer in #697 and #698. Previously this required two_factor_user_api_login_enable filter to be set to true which is now the default during application password auth. XML-RPC login is still disabled for regular user passwords.
Features: Label recommended methods to simplify the configuration by @kasparsd in #676 and #675
Documentation: Add WP.org plugin demo by @kasparsd in #667
Documentation: Document supported versions of WP core and PHP by @jeffpaul in #695
Documentation: Document the release process by @jeffpaul in #684
Tooling: Remove duplicate WP.org screenshots and graphics from SVN trunk by @jeffpaul in #683

0.13.0 – 2025-04-02

Add two_factor_providers_for_user filter to limit two-factor providers available to each user by @kasparsd in #669
Update automated testing to cover PHP 8.4 and default to PHP 8.3 by @BrookeDot in #665

View the complete changelog details here.

Excellent

Work as expect

Users can undermine, only suitable for admin

worked and super fast support time.