Quick answers
- Is CVE-2026-118185 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118185 being exploited in the wild.
- How severe is CVE-2026-118185?
- Informational severity, published 31 October 2026.
- Which products and versions are affected?
- WPScan Security Optimizer before 1.6.9.
- Is there a fix for CVE-2026-118185?
- Yes: fixed in 1.6.9. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118185 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-118185?
- Check whether you run WPScan Security Optimizer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.6.9
Technical details
The plugin lacks rate limiting on 2FA code submission attempts during account login. An attacker with knowledge of a valid username and password can repeatedly submit different 2FA codes without throttling, enabling a brute-force attack on the second authentication factor. This is a broken authentication vulnerability (CWE-287) that can be exploited over the network from outside the organization.
Affected products
- WPScan Security Optimizer before 1.6.9
Timeline
- 2026-10-31: disclosed
- 2026-10-29: advisory