CVE-2026-119616 json
Noptin <= 4.4.3 - Unauthenticated Local File Inclusion via 'the_template_path' Merge-Tag Attribute via Stored Subscriber first_name
published 2026-11-07 2 d ago modified 2026-11-08 20 h ago also EUVD-2026-118559
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
The Noptin – Newsletter, New Post Notifications & Email Automation plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.4.3 via the 'noptin_fields[first_name]' parameter parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. The public Manage Preferences page issues a nonce to unauthenticated visitors, meaning there is no effective authorization barrier — an unauthenticated attacker can store the malicious payload as their first_name and have it executed the next time any newsletter is sent by the site operator. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 20 h ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N |
Affected products
- picocodes Noptin – Newsletter, New Post Notifications & Email Automation
Classification
- Weakness
-
- CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program
- Technology feeds
References
- github.com /hizzle-co/noptin/commit/f5ea148ad1b7744d27b20244795d63092267f497
- wordfence.com /threat-intel/vulnerabilities/id/463de4fc-c5c2-43f9-86e9-686004447561?source=cve
- plugins.trac.wordpress.org /browser/newsletter-optin-box/tags/4.4.3/build/Core/functions.php#L364
- plugins.trac.wordpress.org /browser/newsletter-optin-box/tags/4.4.3/build/Core/functions.php#L361
- plugins.trac.wordpress.org /browser/newsletter-optin-box/tags/4.4.3/build/Emails/Generate/Merge_Tags.php#L757
- plugins.trac.wordpress.org /browser/newsletter-optin-box/tags/4.4.3/build/Emails/Generate/Merge_Tags.php#L358
- plugins.trac.wordpress.org /browser/newsletter-optin-box/tags/4.4.3/build/Subscribers/Manage_Preferences.php#L248
- plugins.trac.wordpress.org /changeset/3783142/newsletter-optin-box/trunk/build/Core/functions.php
Sources
- CVE List CVE-2026-119616
- NVD CVE-2026-119616
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.