跳至主要內容
WordPress.org

Taiwan 正體中文

  • 佈景主題目錄
  • 外掛目錄
  • 最新消息
  • 技術支援
  • 關於我們
  • 團隊
  • 取得 WordPress
取得 WordPress
WordPress.org

Plugin Directory

DB Solution – 2FA

  • 提交外掛
  • 我的最愛
  • 登入
  • 提交外掛
  • 我的最愛
  • 登入

DB Solution – 2FA

由 Davide Baraldi 開發
下載
  • 詳細資料
  • 使用者評論
  • 安裝方式
  • 開發資訊
技術支援

外掛說明

DB Solution – 2FA is a practical login security module for WordPress sites that need stronger access control without forcing every protection on by default.

It helps site owners add email OTP verification, protect the standard login path, monitor successful logins, review failed attempts, and block unwanted IP addresses from one focused DB Solution panel.

Key Features

  • 🔐 Email 2FA – Sends a one-time code after the password step, using the WordPress email system already configured on the site.
  • 🧭 Custom Login URL – Replaces the standard login path with a private slug chosen by the site owner.
  • 👀 Login Monitoring – Sends an email notification after successful access, so unusual logins are easier to notice.
  • 🧱 IP Blocking – Blocks single IP addresses and CIDR ranges from the plugin settings panel.
  • 🧾 Access Attempt Log – Shows login attempts with credential, IP address, browser, date, and result, without storing passwords.
  • ⏱️ OTP Countdown – Shows how long the verification code remains valid on the 2FA screen.
  • 🛡️ Strict Mode – Can bind the OTP check to the same IP address and browser that requested it.
  • 🎛️ Modular Controls – Every protection stays disabled after activation until the site owner chooses what to enable.

Why It Helps

Most login security tools enable too much at once or hide the important choices. DB Solution – 2FA keeps the workflow simple: activate the plugin, confirm that email delivery works, then enable only the protections the site actually needs.

This makes it useful for client sites, staging sites, and small business WordPress installs where login security must be stronger without making daily access confusing.

Email Requirement

Email-based 2FA requires a working WordPress email system. Before enabling it, send a test email from the site and confirm that users can receive the OTP code.

Compatibility

  • WordPress: 6.4 through 7.0.
  • PHP: 8.0 or later. Tested on PHP 8.4.18 in the local WordPress 7 test site.

螢幕擷圖

DB Solution dashboard.
DB Solution dashboard.
Settings panel with separate security features.
Settings panel with separate security features.
Security guide and credits.
Security guide and credits.

安裝方式

  1. Upload the db-solution-2fa folder to /wp-content/plugins/.
  2. Activate the plugin from the WordPress Plugins screen.
  3. Open the DB Solution menu and enable only the protections needed by the site.

常見問題集

Does 2FA turn on automatically after plugin activation?

No. Every protection remains disabled until the site owner enables it from the DB Solution settings panel.

Do I need a working email system?

Yes. Email 2FA sends OTP codes through the WordPress email system, so mail delivery must work before enabling 2FA.

Does the access attempt log store passwords?

No. The log stores the attempted username or email, IP address, browser, date, and result. Passwords are never stored.

Can I block IP ranges?

Yes. The IP blocking section supports single IP addresses and CIDR ranges.

Can I keep the normal WordPress login URL?

Yes. The custom login URL is optional and remains disabled until you enable it.

What happens if I disable a feature?

The site returns to the standard WordPress behavior for that feature.

使用者評論

這個外掛目前沒有任何使用者評論。

參與者及開發者

以下人員參與了開源軟體〈DB Solution – 2FA〉的開發相關工作。

參與者
  • Davide Baraldi

將〈DB Solution – 2FA〉外掛本地化為台灣繁體中文版

對開發相關資訊感興趣?

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

變更記錄

16.3

  • Update: aligned the plugin version and stable tag to 16.3.
  • Compatibility: requires WordPress 6.4 or later and PHP 8.0 or later.
  • Compatibility: tested up to WordPress 7.0.
  • Update: added the plugin and author website links to the plugin header.

16.0

  • Fix: the custom login URL no longer replaces WordPress login URLs globally, so the hidden slug is not exposed by normal login redirects.
  • Update: expanded the WordPress.org description with feature highlights and FAQ content.

15.13

  • Fix: sanitized the AJAX option value in a way accepted by WordPress coding standards.
  • Fix: preserved the login remember-me choice without reading unsanitized form data directly.
  • Update: declared compatibility through WordPress 7.0 for the WordPress 7 test site.
  • Update: rewrote the readme short description and description in standard English.

15.12

  • Security: added a 5-attempt limit for each OTP code.
  • Security: the remember-me cookie is used only when selected by the user.

15.11

  • Fix: removed inline helper functions unavailable in the login context to avoid fatal errors.

15.10

  • Update: added the countdown to the 2FA verification screen.
  • Update: updated the email footer with the site name and plugin by Unicorn Designer.

15.9

  • Update: main toggles and simple fields now save automatically without a general save button.
  • Update: the manual save button remains only in the IP blocking card with the label Save blocked IPs.

15.8

  • Update: redesigned the settings interface with custom cards, icons, and colors.
  • Update: replaced classic WordPress tabs with pill navigation.
  • Compatibility: kept the code compatible with PHP 8.3 and PHP 8.4 without PHP 8.5-only features.

15.7

  • Update: removed the large header card from the settings page.
  • Update: refreshed the settings design with lighter cards.
  • New: added the access attempts tab with username or email, IP address, browser, date, and result.
  • Security: attempted passwords are never stored in the log.

15.6

  • Update: removed the global switch from the interface and public logic.
  • New: added the IP blocking section with support for single IP addresses and CIDR networks.
  • Update: refreshed the admin design for settings, guide, and credits.

15.5

  • Update: declared compatibility through WordPress 6.9.
  • Update: separated the global control from 2FA activation.
  • New: added a dedicated Enable Email 2FA option.
  • New: added a confirmation notice before enabling email-based 2FA.
  • Fix: login monitoring works even when 2FA is not active.
  • Update: rewrote guide and credits text.

15.4

  • New: added Strict Mode security that locks OTP verification to IP address and user agent.
  • New: added OTP expiration time setting.
  • New: added settings saved confirmation message.
  • Fix: sanitized server variables and inputs according to WordPress coding standards.

15.3

  • Fix: moved CSS and JS to external files and enqueued them properly.
  • Fix: removed the assets folder from the plugin ZIP.

15.2

  • Update: renamed plugin slug, text domain, and prefixes to db-solution-2fa.

15.1.5

  • Security improvements: strict sanitization and nonce checks.
  • Removed the internal updater to comply with WordPress.org repository standards.

15.1.1

  • Standard fix for WordPress.org compliance.

15.1.0

  • Full integration into the DB Solution suite.
  • New modular and modern user interface.
  • Code refactoring for performance and security.

15.0.0

  • Previous standalone version.

中繼資料

  • 版本 16.3
  • 最後更新 2 週前
  • 啟用安裝數 10+
  • WordPress 版本需求 6.4 或更新版本
  • 已測試相容的 WordPress 版本 7.0.4
  • PHP 版本需求 8.0 或更新版本
  • 語言
    English (US)
  • 標籤:
    2FAauthenticationcustom loginprotectionsecurity
  • 進階檢視

評分

這個項目尚無任何評論記錄。

撰寫評分

查看全部使用者評論

參與者

  • Davide Baraldi

技術支援

使用者可在技術支援論壇提出意見反應或使用問題。

檢視技術支援論壇

  • 關於我們
  • 最新消息
  • 主機代管
  • 隱私權
  • 展示網站
  • 佈景主題目錄
  • 外掛目錄
  • 區塊版面配置目錄
  • Learn
  • 技術支援
  • 開發者資源
  • WordPress.tv ↗
  • 共同參與
  • 活動
  • 贊助基金會 ↗
  • Swag ↗
  • WordPress.com ↗
  • Matt ↗
  • bbPress ↗
  • BuddyPress ↗
WordPress.org
WordPress.org

Taiwan 正體中文

  • 查看我們的 X (之前的 Twitter) 帳號
  • 造訪我們的 Bluesky 帳號
  • 造訪我們的 Mastodon 帳號
  • 造訪我們的 Threads 帳號
  • 造訪我們的 Facebook 粉絲專頁
  • Visit our Instagram account
  • Visit our LinkedIn account
  • 造訪我們的 TikTok 帳號
  • Visit our YouTube channel
  • 造訪我們的 Tumblr 帳號
程式碼,如詩
The WordPress® trademark is the intellectual property of the WordPress Foundation.