Title: OOSOFT 2FA Security
Author: oosoft
Published: <strong>aprel 28, 2026</strong>
Last modified: aprel 28, 2026

---

Search plugins

![](https://ps.w.org/oosoft-2fa-security/assets/icon-256x256.png?rev=3518666)

# OOSOFT 2FA Security

 By [oosoft](https://profiles.wordpress.org/oosoft/)

[Download](https://downloads.wordpress.org/plugin/oosoft-2fa-security.zip)

 * [Details](https://tuk.wordpress.org/plugins/oosoft-2fa-security/#description)
 * [Reviews](https://tuk.wordpress.org/plugins/oosoft-2fa-security/#reviews)
 *  [Installation](https://tuk.wordpress.org/plugins/oosoft-2fa-security/#installation)
 * [Development](https://tuk.wordpress.org/plugins/oosoft-2fa-security/#developers)

 [Support](https://wordpress.org/support/plugin/oosoft-2fa-security/)

## Description

OOSOFT 2FA Security adds robust two-factor authentication to your WordPress site.
Protect every login with a second verification step using a TOTP authenticator app(
Google Authenticator, Authy, etc.) or a one-time code sent to your email address.

**Key Features:**

 * **TOTP Authenticator App** — compatible with Google Authenticator, Authy, Microsoft
   Authenticator, and any RFC 6238-compliant app.
 * **Email OTP** — sends a time-limited one-time code to the user’s registered email
   address.
 * **Backup Codes** — generate single-use recovery codes so users are never locked
   out.
 * **Role-Based Enforcement** — require 2FA for specific roles (e.g. administrators)
   while leaving it optional for others.
 * **Rate Limiting** — brute-force protection with configurable attempt limits and
   lockout periods.
 * **Security Logs** — detailed event logging with filterable admin view and automatic
   pruning.
 * **Encrypted Secret Storage** — TOTP secrets are encrypted at rest using libsodium(
   preferred) or AES-256-GCM/CBC via OpenSSL.
 * **HKDF Key Derivation** — encryption keys are derived from your WordPress secret
   keys; no raw key material is stored.

## Installation

 1. Upload the `oosoft-2fa-security` folder to the `/wp-content/plugins/` directory.
 2. Activate the plugin through the **Plugins** menu in WordPress.
 3. Go to **Settings > 2FA Security** to configure enforcement rules and options.
 4. Users can set up their preferred 2FA method from their **Profile** page.

## FAQ

### Which authenticator apps are supported?

Any app that supports the TOTP standard (RFC 6238), including Google Authenticator,
Authy, Microsoft Authenticator, and 1Password.

### What happens if a user loses their authenticator app?

Users can log in with one of their backup codes. Administrators can also disable
2FA for a user from the Users list.

### Is TOTP secret storage secure?

Yes. Secrets are encrypted with AES-256 (libsodium secretbox preferred, OpenSSL 
AES-256-GCM/CBC as fallback) before being stored in the database. Encryption keys
are derived from your site’s unique WordPress secret keys via HKDF-SHA256.

### Does this plugin work with WooCommerce or custom login forms?

The plugin intercepts WordPress’s core authentication pipeline, so it works with
any theme or plugin that uses `wp_signon()` or the standard login form.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“OOSOFT 2FA Security” is open source software. The following people have contributed
to this plugin.

Contributors

 *   [ oosoft ](https://profiles.wordpress.org/oosoft/)
 *   [ OOSOFT ](https://profiles.wordpress.org/mudivillanv/)

[Translate “OOSOFT 2FA Security” into your language.](https://translate.wordpress.org/projects/wp-plugins/oosoft-2fa-security)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/oosoft-2fa-security/),
check out the [SVN repository](https://plugins.svn.wordpress.org/oosoft-2fa-security/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/oosoft-2fa-security/)
by [RSS](https://plugins.trac.wordpress.org/log/oosoft-2fa-security/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.0.2

 * Improved escaping and security hardening throughout.
 * Removed deprecated load_plugin_textdomain() call (WordPress 4.6+ auto-loads translations).
 * Added HKDF key derivation fallback warning when WordPress secret keys are not
   configured.

#### 1.0.1

 * Fixed QR code scanning compatibility with major authenticator apps.
 * Switched to proven qrcodejs library for QR generation.

#### 1.0.0

 * Initial release.

## Meta

 *  Version **1.0.2**
 *  Last updated **2 weeks ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.0 or higher **
 *  Tested up to **6.9.4**
 *  PHP version ** 8.0 or higher **
 *  Language
 * [English (US)](https://wordpress.org/plugins/oosoft-2fa-security/)
 * Tags
 * [2FA](https://tuk.wordpress.org/plugins/tags/2fa/)[otp](https://tuk.wordpress.org/plugins/tags/otp/)
   [security](https://tuk.wordpress.org/plugins/tags/security/)[totp](https://tuk.wordpress.org/plugins/tags/totp/)
   [two factor authentication](https://tuk.wordpress.org/plugins/tags/two-factor-authentication/)
 *  [Advanced View](https://tuk.wordpress.org/plugins/oosoft-2fa-security/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/oosoft-2fa-security/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/oosoft-2fa-security/reviews/)

## Contributors

 *   [ oosoft ](https://profiles.wordpress.org/oosoft/)
 *   [ OOSOFT ](https://profiles.wordpress.org/mudivillanv/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/oosoft-2fa-security/)