CVE-2026-118202 · Package
NO FIX YET
The Limit Login Attempts Security WordPress plugin before 3.4.1 does not confirm its two-factor authentication step succeeded before completing a login. An attacker who knows a protected user's password can skip the second factor by sending a crafted request header.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Sites running the Limit Login Attempts Security WordPress plugin before 3.4.1 that use its two-factor authentication for user logins. An attacker still needs a protected user's password, so sites without two-factor enabled for that plugin are not exposed through this flaw.
Not affected if plugin-at-3.4.1-or-later, two-factor-not-enabled
Who cares self-hosted, two-factor-auth, wordpress
3.4.1.Unknown from the sources.
The Limit Login Attempts Security WordPress plugin before 3.4.1 does not confirm that its two-factor authentication step succeeded before completing a login and treats a failure to build that step as success, so an attacker who holds a protected user's password can bypass the second factor by sending a request header that breaks the step.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.