CVE-2026-84777

Really Simple Security – Simple and Performant Security (formerly Really Simple SSL) <= 9.8.0 - Unauthenticated Two-Factor Authentication Bypass

2026-09-02 00:00
Ananda Dhakal

Strategic Overview

Status
Patched in 9.8.1
Affected Plugin
Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)
Affected Version
<= 9.8.0
CVSS
5.3Medium
Weakness type
CWE-287 · Improper Authentication
CVE
CVE-2026-84777
View all Really Simple Security – Simple and Performant Security (formerly Really Simple SSL) vulnerabilities

At a glance

CVE-2026-84777 is a medium-severity Improper Authentication vulnerability in the Really Simple Security WordPress plugin, affecting versions <= 9.8.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 9.8.1; sites on affected versions should update now. Disclosed September 2026, reported by Ananda Dhakal.

Vulnerability Overview

The Really Simple Security – Simple and Performant Security (formerly Really Simple SSL) plugin for WordPress is vulnerable to 2FA Bypass in all versions up to, and including, 9.8.0. This makes it possible for unauthenticated attackers to bypass 2FA.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-287: Improper Authentication

Reaching this weakness in Really Simple Security <= 9.8.0 takes no account at all. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For Really Simple Security the fix is 9.8.1: builds <= 9.8.0 are affected, anything from 9.8.1 onward is not.

Remediation

Update to version 9.8.1, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Really Simple Security 9.8.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-84777https://www.wordfence.com/threat-intel/vulnerabilities/id/7708ec57-96d9-4250-b36a-f9ea79ef18dahttps://nvd.nist.gov/vuln/detail/CVE-2026-84777

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C