CVE-2026-103482 json
Simple Newsletter Plugin <= 4.3.10 - Unauthenticated Stored Cross-Site Scripting via Subscriber Custom Field via Manage Preferences Form + Campaign Preview noptin_key Pivot
published 30d ago modified 27d ago also EUVD-2026-96112
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-103482 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 29d ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- picocodes Noptin – Newsletter, New Post Notifications & Email Automation
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/e5f8afa3-f20c-4dfb-bcc6-2682f68723ca?source=cve
- plugins.trac.wordpress.org /browser/newsletter-optin-box/tags/4.3.10/build/Emails/Preview.php#L161
- plugins.trac.wordpress.org /browser/newsletter-optin-box/tags/4.3.10/build/Emails/Generate/Generator.php#L548
- plugins.trac.wordpress.org /browser/newsletter-optin-box/tags/4.3.10/build/Core/Dynamic_Content_Tags.php#L507
- plugins.trac.wordpress.org /browser/newsletter-optin-box/tags/4.3.10/build/Core/Dynamic_Content_Tags.php#L361
- plugins.trac.wordpress.org /browser/newsletter-optin-box/tags/4.3.10/build/Core/Dynamic_Content_Tags.php#L695
- plugins.trac.wordpress.org /browser/newsletter-optin-box/tags/4.3.10/build/Subscribers/functions.php#L937
- plugins.trac.wordpress.org /browser/newsletter-optin-box/tags/4.3.10/build/Subscribers/Manage_Preferences.php#L255
- plugins.trac.wordpress.org /browser/newsletter-optin-box/tags/4.3.10/vendor/hizzle/store/src/Prop.php#L626
- github.com /hizzle-co/noptin/compare/4.3.10...4.4.0
Sources
- CVE List CVE-2026-103482
- NVD CVE-2026-103482
Fencer Intel 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.