Skip to main content

WP 2FA CVE-2026-103514

| EUVDEUVD-2026-91934 HIGH
Improper Authentication (CWE-287)
2026-10-03 WPScan GHSA-fh83-crgf-9w82
7.5
CVSS 3.1 · Vendor: WPScan
Share

Severity by source

Vendor (WPScan) PRIMARY
7.5 HIGH
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.5 HIGH

AC:H because the attacker must capture and replay a TOTP within its short window; PR:L because valid account credentials are a precondition; full C/I/A:H as 2FA bypass fully compromises the account.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

6
POC Analysis Generated
Oct 03, 2026 - 19:21 vuln.today
Analysis Generated
Oct 03, 2026 - 16:23 vuln.today
CVSS changed
Oct 03, 2026 - 16:22 NVD
7.5 (HIGH)
Patch available
Oct 03, 2026 - 07:00 EUVD
CVE Published
Oct 03, 2026 - 06:00 cve.org
HIGH 7.5
CVE Published
Oct 03, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

AnalysisAI

TOTP replay in the WP 2FA WordPress plugin (versions before 4.1.0) allows an attacker who already knows an account's password and can capture a valid time-based one-time passcode within its ~30-second validity window to reuse that same code and complete login without ever knowing the second factor - including on administrator accounts. The defect (CWE-287, improper authentication) is that consumed codes are never invalidated, so replays succeed while the code is still live; this does not allow bypass from scratch, since it requires prior credential compromise plus real-time observation of a code via phishing, a proxy, MITM, or logging. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

No credit card · 7-day full trial

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Exploitation requires two concrete, attacker-controlled-only-in-part prerequisites: (1) the attacker must already know the target account's password, and (2) the attacker must observe or intercept a valid time-based one-time passcode and replay it before its short validity window (typically ~30 seconds) expires - the plugin's failure to invalidate a consumed TOTP is the core defect. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment This is a genuine but conditional authentication-bypass flaw rather than a mass-exploitation emergency. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation Vendor-released patch: upgrade the WP 2FA plugin to version 4.1.0 or later, which adds invalidation of consumed one-time passcodes; the fix is documented via the WPScan advisory at https://wpscan.com/vulnerability/e05aa5a3-cd04-428a-b6bb-0538ca1f6b4a/ and the NVD entry https://nvd.nist.gov/vuln/detail/CVE-2026-103514, and should be deployed along with a rotation of WordPress passwords for any account suspected of credential compromise. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours, inventory all WordPress installations using the WP 2FA plugin and identify any version below 4.1.0; immediately update those sites to WP 2FA 4.1.0, or if an update cannot be applied, disable the plugin until patching is possible, and review authentication logs for suspicious administrator logins. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

More in Wp 2Fa

View all

Share

CVE-2026-103514 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy