Title: DB Solution Ìtumọ̀ Yorùbá: – 2FA Author: Davide Baraldi Published: Èrèlé 13, 2026 Last modified: Ọwẹ́wẹ̀ 18, 2026 --- Ṣàwárí àwọn plugin ![](https://ps.w.org/db-solution-2fa/assets/banner-772x250.jpg?rev=3627298) ![](https://ps.w.org/db-solution-2fa/assets/icon-256x256.jpg?rev=3627298) # DB Solution Ìtumọ̀ Yorùbá: – 2FA Láti ọwọ́ [Davide Baraldi](https://profiles.wordpress.org/davidebaraldi/) [Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/db-solution-2fa.16.5.zip) * [Àwọn àlàyé](https://yor.wordpress.org/plugins/db-solution-2fa/#description) * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/db-solution-2fa/#reviews) * [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/db-solution-2fa/#installation) * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/db-solution-2fa/#developers) [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/db-solution-2fa/) ## Àpèjúwe DB Solution Ìtumọ̀ Yorùbá: – 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 Ìtumọ̀ Yorùbá: – Sends a one-time code after the password step, using the WordPress email system already configured on the site. * 🧭 Custom Login URL Ìtumọ̀ Yorùbá: – Replaces the standard login path with a private slug chosen by the site owner. * 👀 Login Monitoring Ìtumọ̀ Yorùbá: – Sends an email notification after successful access, so unusual logins are easier to notice. * 🧱 IP Blocking Ìtumọ̀ Yorùbá: – Blocks single IP addresses and CIDR ranges from the plugin settings panel. * 🧾 Access Attempt Log Ìtumọ̀ Yorùbá: – Shows login attempts with credential, IP address, browser, date, and result, without storing passwords. * ⏱️ OTP Countdown Ìtumọ̀ Yorùbá: – Shows how long the verification code remains valid on the 2FA screen. * 🛡️ Strict Mode Ìtumọ̀ Yorùbá: – Can bind the OTP check to the same IP address and browser that requested it. * 🎛️ Modular Controls Ìtumọ̀ Yorùbá: – 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 Ìtumọ̀ Yorùbá: – 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. ## Àwọn àwòrán ìbòjú [⌊DB Solution dashboard.⌉⌊DB Solution dashboard.⌉[ DB Solution dashboard. [⌊Settings panel with separate security features.⌉⌊Settings panel with separate security features.⌉[ Settings panel with separate security features. [⌊Security guide and credits.⌉⌊Security guide and credits.⌉[ Security guide and credits. [[ [[ [[ [[ [[ ## Ìgbéwọlẹ̀ 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. ## FAQ ### 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. ## Àwọn àgbéyẹ̀wò Kò sí àwọn àgbéyẹ̀wò fún plugin yìí. ## Àwọn Olùkópa & Olùgbéejáde “DB Solution Ìtumọ̀ Yorùbá: – 2FA” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí. Àwọn Olùkópa * [ Davide Baraldi ](https://profiles.wordpress.org/davidebaraldi/) [Túmọ̀ “DB Solution Ìtumọ̀ Yorùbá: – 2FA” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/db-solution-2fa) ### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè? [Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/db-solution-2fa/), ṣàyẹ̀wò [ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/db-solution-2fa/), tàbí ṣe àgbékalẹ̀ sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/db-solution-2fa/) nípasẹ̀ [RSS](https://plugins.trac.wordpress.org/log/db-solution-2fa/?limit=100&mode=stop_on_copy&format=rss). ## Àkọsílẹ̀ àwọn àyípadà #### 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. ## Àkójọpọ̀ Meta * Ẹ̀yà **16.5** * Ìgbàgbọ́hùn tó kẹ́yìn **ọ̀sẹ̀ 1 sẹ́yìn** * Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **10+** * Ẹ̀yà WordPress ** 6.4 tàbí ju bẹ́ẹ̀ lọ ** * Dánwò dé **7.0.6** * Ẹ̀yà PHP ** 8.0 tàbí ju bẹ́ẹ̀ lọ ** * Èdè * [English (US)](https://wordpress.org/plugins/db-solution-2fa/) * Àwọn àmì * [2FA](https://yor.wordpress.org/plugins/tags/2fa/)[authentication](https://yor.wordpress.org/plugins/tags/authentication/) [custom login](https://yor.wordpress.org/plugins/tags/custom-login/)[protection](https://yor.wordpress.org/plugins/tags/protection/) [security](https://yor.wordpress.org/plugins/tags/security/) * [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/db-solution-2fa/advanced/) ## Àwọn ìbò Kò sí ìwádìí tí a tíì fi ránṣẹ́. [Your review](https://wordpress.org/support/plugin/db-solution-2fa/reviews/#new-post) [Wo gbogbo àwọn àgbéyẹ̀wò](https://wordpress.org/support/plugin/db-solution-2fa/reviews/) ## Àwọn Olùkópa * [ Davide Baraldi ](https://profiles.wordpress.org/davidebaraldi/) ## Ìrànlọ́wọ́ Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́? [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/db-solution-2fa/)