WordPress.org

Taiwan 正體中文

取得 WordPress
WordPress.org

Plugin Directory

Two Factor

Two Factor

由 WordPress.org 開發
下載

外掛說明

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. There are no site-wide settings for this plugin.

個人使用者

  1. Navigate to your profile: Go to “Users” “Your Profile” in the WordPress admin
  2. Find Two-Factor Options: Scroll down to the “Two-Factor Options” section
  3. 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
    • FIDO U2F Security Keys – Use physical security keys (requires HTTPS)
    • Backup Codes – Generate one-time backup codes for emergencies
    • Dummy Method – For testing purposes only (requires WP_DEBUG)
  4. Configure each method: Follow the setup instructions for each enabled provider
  5. Set primary method: Choose which method to use as your default authentication
  6. Save changes: Click “Update Profile” to save your settings

網站管理員

  • No global settings: This plugin operates on a per-user basis only. For more, see GH#249.
  • 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

Available Authentication Methods

驗證碼產生器 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 Security Keys

  • Security: High – Hardware-based authentication
  • Setup: Register physical security keys (USB, NFC, or Bluetooth)
  • Requirements: HTTPS connection required, compatible browser needed
  • Browser Support: Chrome, Firefox, Edge (varies by key type)
  • Best for: Users with security keys who want maximum security

Dummy Method

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

Important Notes

HTTPS Requirement

  • FIDO U2F Security Keys require an HTTPS connection to function
  • Other methods work on both HTTP and HTTPS sites

Browser Compatibility

  • FIDO U2F requires a compatible browser and may not work on all devices
  • TOTP and email methods work on all devices and browsers

Account Recovery

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

Security Best Practices

  • 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_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_inputaction which receives the provider object and fires after the input shown on the authentication input form (if form contains no input, action fires immediately after two_factor_after_authentication_prompt).

螢幕擷圖

  • Two-factor options under User Profile – Shows the main configuration area where users can enable different authentication methods.
  • U2F Security Keys section under User Profile – Displays the security key management interface for registering and managing FIDO U2F devices.
  • 登入 WordPress 後，使用電子郵件傳送驗證碼進行驗證：在登入期間顯示電子郵件驗證畫面
  • Authenticator App (TOTP) setup with QR code – Demonstrates the QR code generation and manual key entry for TOTP setup.

常見問題集

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

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

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

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

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

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

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

Why doesn’t this plugin have site-wide settings?

This plugin is designed to work on a per-user basis, allowing each user to choose their preferred authentication methods. This approach provides maximum flexibility and security. Site administrators can still configure 2FA for other users by editing their profiles. For more information, see issue #437.

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 currently supports FIDO U2F, which is the predecessor to WebAuthn. For full WebAuthn support, you may want to look into additional plugins that extend this functionality. The current U2F implementation requires HTTPS and has browser compatibility limitations.

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: https://wordpress.org/plugins/two-factor-provider-webauthn/
. It integrates directly with Two-Factor and adds WebAuthn-based authentication as an additional two-factor option for users.

使用者評論

Two Factor = PERFECT

2026 年 2 月 24 日
It’s rare to see a plugin that’s so efficient, reliable, and without any complications. Simply brilliant!

A quick and easy way to secure your admin account(s)

2026 年 1 月 15 日
Install, activate. Go to your user profile and add your 2FA with your password manager/authentication app. Done. So easy and efficient. No bells and whistles, but if securing your admin account(s) is all that matters, it’s the best and easiest option. Thanks to the team for this!
閱讀全部 199 則使用者評論

參與者及開發者

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

參與者

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

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

對開發相關資訊感興趣？

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

變更記錄

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.

社群版外掛

這個外掛由社群人員開發及提供技術支援。 參與這個外掛專案

中繼資料

評分

4.8 星，滿分為 5 星

新增使用者評論

查看全部使用者評論

技術支援

最近 2 個月解決的問題:

總計 6 個問題，已解決 3 個

檢視技術支援論壇