Answer in brief
CVE-2026-119616 records a Medium severity (CVSS 5.9) vulnerability in Noptin <= 4.4.3 - Unauthenticated Local File Inclusion via 'the_template_path' Merge-Tag Attribute via Stored Subscriber first_name. The current sources do not mark it as known exploited. The current feed maps picocodes/Noptin – Newsletter, New Post Notifications & Email Automation (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps picocodes/Noptin – Newsletter, New Post Notifications & Email Automation (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| picocodes/Noptin – Newsletter, New Post Notifications & Email Automationgeneric | >=0 <=4.4.3 | Not reported |
Published upstream
Nov 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 7, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 7, 2026
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.
Quoted source text, attributed separately from HOL analysis.