Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-103482 Overview
The Simple Newsletter Plugin – Noptin for WordPress contains a stored cross-site scripting (XSS) vulnerability [CWE-79] in versions up to and including 4.3.10. The flaw resides in the handling of the noptin_fields[<custom_field_merge_tag>] parameter, such as first_name, due to insufficient input sanitization and output escaping. Unauthenticated attackers can inject arbitrary web scripts that execute when users access an affected page. Exploitation requires a published campaign post whose body contains a [[subscriber.*]] merge tag, plus a social-engineering step targeting a privileged user.
Critical Impact
Unauthenticated attackers can achieve script execution in a privileged user's browser session by chaining a public form submission with a crafted campaign preview URL.
Affected Products
- Simple Newsletter Plugin – Noptin for WordPress, all versions up to and including 4.3.10
- WordPress sites running Noptin with at least one published campaign using [[subscriber.*]] merge tags
- Administrator and editor accounts targeted via the campaign preview URL
Discovery Timeline
- 2026-10-10 - CVE-2026-103482 published to NVD
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-103482
Vulnerability Analysis
The vulnerability is a stored cross-site scripting flaw in Noptin's dynamic content tag system. When Noptin renders a campaign that contains a [[subscriber.*]] merge tag, the plugin resolves subscriber field values through Dynamic_Content_Tags.php and related generation code. These values are read from subscriber-controlled custom fields without sufficient sanitization or output escaping, allowing injected markup to reach the rendered page.
The attack chain is multi-step. An unauthenticated attacker first submits an entity-encoded payload to the public manage_preferences form, which issues its own nonce on the same page and stores the payload against a subscriber record. The attacker then embeds the subscriber's confirm_key into a campaign preview URL and delivers it to a privileged WordPress user through social engineering. When the privileged user opens the preview, the payload decodes and executes in the browser under the WordPress site origin.
Root Cause
The root cause is improper neutralization of input during web page generation. Subscriber-controlled field values are expanded into campaign output through merge-tag substitution in build/Core/Dynamic_Content_Tags.php, build/Emails/Generate/Generator.php, and build/Emails/Preview.php without escaping context-appropriate HTML. The entity-encoded storage path hides the payload from naive input filters, and output rendering decodes the value back into executable markup.
Attack Vector
The attack vector is network-based and requires no authentication, but exploitation complexity is high because it depends on an existing campaign that uses subscriber merge tags and a social-engineering step to make a privileged user open the crafted preview URL. The scope is changed because script execution occurs in the authenticated session context of the targeted user, enabling actions on their behalf within the WordPress admin interface.
No verified public proof-of-concept code is available. Refer to the Wordfence Vulnerability Report and the vulnerable code locations in build/Subscribers/Manage_Preferences.php and build/Core/Dynamic_Content_Tags.php for technical details.
Detection Methods for CVE-2026-103482
Indicators of Compromise
- POST requests to the public manage_preferences endpoint containing HTML entity-encoded sequences such as <script or <script in noptin_fields[*] parameters
- Campaign preview URLs sent to administrators that include a confirm_key parameter tied to a recently created or modified subscriber
- Subscriber records whose custom field values, including first_name, contain <script>, onerror=, or javascript: fragments after decoding
Detection Strategies
- Inspect WordPress access logs for unauthenticated POSTs to Noptin preference endpoints followed shortly by GET requests to campaign preview URLs referencing the same confirm_key
- Query the Noptin subscribers table for custom field values containing HTML tags or encoded script fragments
- Alert on administrator browser sessions executing unexpected inline scripts originating from Noptin-rendered campaign pages
Monitoring Recommendations
- Monitor the Noptin plugin version across all WordPress installations and flag any instance at or below 4.3.10
- Track creation and editing of subscriber custom fields by unauthenticated IPs, especially bursts targeting a single site
- Review web application firewall telemetry for XSS payload patterns against /wp-admin/admin-ajax.php and public Noptin form handlers
How to Mitigate CVE-2026-103482
Immediate Actions Required
- Update the Simple Newsletter Plugin – Noptin to version 4.4.0 or later on every affected WordPress site
- Audit published campaigns and remove or neutralize any [[subscriber.*]] merge tags until the upgrade is complete
- Review subscriber custom field values and purge records containing HTML or script content
Patch Information
The vendor fixed the issue in Noptin 4.4.0. See the GitHub Comparison Release Notes for the complete set of changes between 4.3.10 and 4.4.0, including the sanitization and output escaping updates applied to the dynamic content tag pipeline.
Workarounds
- Disable the Noptin plugin until the patched version can be deployed if campaigns rely on subscriber merge tags
- Remove [[subscriber.*]] merge tags from all published campaign bodies to break the exploitation chain
- Deploy a web application firewall rule to block POST requests to manage_preferences that contain HTML entity-encoded script tokens in noptin_fields[*] parameters
# Configuration example
wp plugin update newsletter-optin-box --version=4.4.0
wp plugin list --name=newsletter-optin-box --fields=name,status,version
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

