Skip to main content
CVE-2026-119616VulnerabilityPublished

The Noptin – Newsletter, New Post Notifications & Email Automation plugin for WordPress is vulnerable to Local File

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-119616· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium.

Data as of 7 Nov 2026, 04:36 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.15.9
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 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 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
picocodesNoptin – Newsletter, New Post Notifications & Email AutomationAffected
  • <=4.4.3
Fixed in–

AI-suggested

Administrators should avoid sending newsletters until a fix is available or implement manual validation and sanitization of input fields to prevent malicious payload injection. Monitoring plugin updates from the vendor is recommended to apply an official fix once released.

Description

The Noptin WordPress plugin up to version 4.4.3 is vulnerable to a Local File Inclusion (LFI) flaw via the 'noptin_fields[first_name]' parameter. This vulnerability allows unauthenticated attackers to include and execute arbitrary PHP files on the server. Exploitation requires an administrator to trigger the sending of a newsletter containing the malicious payload, as unauthenticated users can store PHP code in the first_name field but cannot directly execute it. The vulnerability can lead to code execution, bypassing access controls and potential data exposure.

References

Community reviews

Loading reviews…