CVE-2026-118185VulnerabilityPublished 31 Oct 2026

The Security Optimizer WordPress plugin before 1.6.9 does not limit the number of two-factor authentication codes that

Source GCVE Database

Compare

Authoritative record:CVE-2026-118185· High

Not known to be exploited : upgrade to 1.6.9 soon.

Data as of 31 Oct 2026, 07:08 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 1.6.9

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-9wr6-gc4g-7v5m

What to do

Upgrade Security Optimizer (WordPress plugin) to 1.6.9.

Affected software

Product	Affected	Fixed in
Security Optimizer	Affected <1.6.9	Fixed in 1.6.9

AI-suggested

Upgrade the Security Optimizer WordPress plugin to version 1.6.9 or later, where this vulnerability is addressed. No other mitigation steps are indicated as the fix is available in the updated plugin version.

Description

The Security Optimizer WordPress plugin versions before 1.6.9 have a vulnerability where the number of two-factor authentication (2FA) code submissions for a pending login is not limited. This flaw allows an attacker who already knows a user's password to brute force the second factor and gain unauthorized access to the account.

Impact

An attacker with knowledge of a user's password can brute force the second factor of authentication due to the absence of submission limits on 2FA codes. This leads to full account compromise despite the presence of two-factor authentication, undermining the security benefits of 2FA and potentially exposing sensitive user data or administrative controls.

Summary

The Security Optimizer WordPress plugin prior to version 1.6.9 does not enforce a limit on the number of two-factor authentication codes that can be submitted during a pending login session. This lack of rate limiting enables an attacker, who has already compromised a user's password, to repeatedly attempt 2FA codes until successful, effectively bypassing the second authentication factor and taking over the user's account.

References

Community reviews

Loading reviews…