Skip to main content
VulnerabilityPublished

CVE-2026-103514: WP 2FA · Improper Authentication

Affects WP 2FASource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 4.1.0 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.1.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade WP 2FA to 4.1.0.

Affected software

ProductAffectedFixed in
WP 2FAAffected
  • <4.1.0
Fixed in
  • 4.1.0

AI-suggested

Upgrade the WP 2FA plugin to version 4.1.0 or later, where this vulnerability has been addressed. No other mitigation guidance is provided. Patch status is not explicitly stated but the presence of a fixed version (4.1.0) implies an official fix is available.

Description

The WP 2FA WordPress plugin before 4.1.0 does not invalidate a time-based one-time passcode once it has been used, allowing an attacker who knows an account's password and has observed a valid code within its validity window to replay it and bypass two-factor authentication, including on administrator accounts.

References

Community reviews

Loading reviews…