HomeWordPress vulnerabilitiesSimple Newsletter Plugin
Simple Newsletter Plugin vulnerabilities
Simple Newsletter Plugin has 2 known vulnerabilities in this database. The most recent published record is dated 10 Oct 2026.
- Known vulnerabilities
- 2
- Active installs
- 10,000+
- Latest version
- 4.3.10
- Last updated
- 20 Sep 2026
- Most recent
- 10 Oct 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-103482 | Medium 5.4 | Up to 4.3.10 | No fixed version yet | 2 d ago |
| Sensitive data exposure CVE-2026-78146 | Medium 6.5 | Before 4.3.3 | Fixed in 4.3.3 | 26 Aug 2026 |
Read the published descriptions
- CVE-2026-103482, 10 Oct 2026
- The Simple Newsletter Plugin - Noptin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'noptin_fields[<custom_field_merge_tag>] (e.g. first_name)' parameter in all versions up to, and including, 4.3.10 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The attack chain requires a published campaign post whose body contains a [[subscriber.*]] merge tag; the unauthenticated attacker first POSTs the entity-encoded payload to the public manage_preferences form (which issues its own nonce on the same page), then pivots execution by embedding their confirm_key in a campaign preview URL sent to a privileged user via social engineering. CVE record
- CVE-2026-78146, 26 Aug 2026
- The Simple Newsletter Plugin WordPress plugin before 4.3.3 does not verify that the requester is the subscriber named in a public request before rendering that subscriber's stored details, allowing unauthenticated users to disclose a subscriber's personal data along with the key that authorises changes to their record. CVE record
What to do if you run Simple Newsletter Plugin
If you run Simple Newsletter Plugin, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Simple Newsletter Plugin vulnerabilities
Free. We email you when a new vulnerability is published for Simple Newsletter Plugin, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.