CVE-2026-118439VulnerabilityPublished 11 Nov 2026

The Limit Login Attempts Security WordPress plugin before 3.4.2 does not validate the destination of a server-side

Source GCVE Database

Compare

Authoritative record:CVE-2026-118439· High

Not known to be exploited : upgrade to 3.4.2 soon.

Data as of 11 Nov 2026, 07:47 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 3.4.2

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 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 10 Nov 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-8j5v-9pw2-99cj

What to do

Upgrade Limit Login Attempts Security (WordPress plugin) to 3.4.2.

Affected software

Product	Affected	Fixed in
Limit Login Attempts Security	Affected <3.4.2	Fixed in 3.4.2

AI-suggested

Upgrade the Limit Login Attempts Security WordPress plugin to version 3.4.2 or later, where the vulnerability is fixed. No other mitigation steps are indicated.

Description

The Limit Login Attempts Security WordPress plugin versions before 3.4.2 contains a server-side request forgery (SSRF) vulnerability. This flaw allows users with administrator privileges to cause the site to send requests to arbitrary hosts, including internal network addresses, due to lack of validation on a user-supplied setup value.

Impact

An attacker with administrator privileges can exploit this vulnerability to make the WordPress site send requests to arbitrary hosts, potentially accessing internal network resources or services that are not otherwise exposed. This could lead to information disclosure or interaction with internal systems through the vulnerable plugin's SSRF flaw.

Summary

The Limit Login Attempts Security plugin for WordPress, in versions prior to 3.4.2, does not properly validate the destination of server-side requests constructed from user-supplied configuration values. This vulnerability enables an authenticated administrator user to perform SSRF attacks by making the site issue HTTP requests to arbitrary external or internal hosts. No CVSS score is provided, and no public exploits or known in-the-wild exploitation have been reported. The vulnerability is addressed by updating to version 3.4.2 or later.

References

Community reviews

Loading reviews…