Skip to main content
CVE-2026-119039VulnerabilityPublished

The Defender Security WordPress plugin before 6.4.1 does not verify that the client IP address it derives for its

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-119039· High

Not known to be exploited : upgrade to 6.4.1 soon.

Data as of 12 Nov 2026, 07:05 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 6.4.1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 11 Nov 2026.

What to do

Upgrade Defender Security (WordPress plugin) to 6.4.1.

Affected software

ProductAffectedFixed in
Defender SecurityAffected
  • >=4.9.0 <6.4.1
Fixed in
  • 6.4.1

AI-suggested

A fixed version 6.4.1 of the Defender Security WordPress plugin is available that addresses this issue. Users should upgrade to version 6.4.1 or later to ensure proper verification of client IP addresses and prevent IP spoofing attacks. No other mitigation steps are indicated.

Description

The Defender Security WordPress plugin versions before 6.4.1 improperly trust user-supplied IP address values without verifying their source. This flaw allows unauthenticated attackers to spoof IP addresses, bypass IP-based protections such as login lockout and IP banning, impersonate allowlisted IPs, and corrupt activity logs.

References

Community reviews

Loading reviews…