CVE-2026-119616 · Other
NO FIX YET · SEE WHAT TO DO
The Noptin newsletter plugin for WordPress lets unauthenticated visitors store a crafted value in the first_name field, and a Local File Inclusion flaw then includes arbitrary .php files on the server when a newsletter is sent. An attacker can run PHP code, bypass access controls, or read sensitive data once an administrator takes the triggering action.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Noptin plugin for WordPress at version 4.4.3 or earlier are exposed. The flaw is reached through the public Manage Preferences page and the first_name field, and it fires when the site sends a newsletter, so sites that do not run Noptin can skip it.
Not affected if plugin-not-installed, plugin-updated-past-4.4.3
Who cares noptin, self-hosted, wordpress
4.4.3 are affected.4.4.3.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.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N
. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.