Subscribe2 stored XSS via subscriber IP value (CVE-2026-120531)
Identifiers: CVE-2026-120531
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
Wordfence reports a stored cross-site scripting flaw in the Subscribe2 plugin (slug subscribe2) through version 10.47. A visitor can place script in the IP value sent by the AJAX subscription form, which is available when the popup-style signup form is enabled. The stored value is output without escaping and runs in an administrator's browser when the Subscribers list is opened. The 10.48 patched release escapes the IP and email fields on output and validates the IP. As of 9 November 2026, Wordfence also reports that its firewall has blocked attack attempts against this flaw; these are blocked attempts, not confirmed compromises.
Impact
Script executes inside an administrator's session while they review subscribers, which could let an attacker act with those privileges. This is not an unauthenticated admin login or remote code execution flaw. It requires the public popup subscription flow to be available and an administrator to view the list.
Who is affected
Sites running Subscribe2 10.47 or earlier with the popup-style subscription form enabled, which makes the public AJAX signup flow available. Sites on the 10.48 patched release or a newer patched release carry the vendor fix.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| Subscribe2 – Form, Email Subscribers & Newsletters | <= 10.47 | 10.48 |
Exploitation evidence
Exploitation reported. As of 9 November 2026, Wordfence reports that its firewall blocked attack attempts targeting CVE-2026-120531 in the preceding 24 hours; this information was not present the day before. This is vendor-reported telemetry of blocked attempts, not evidence that any site was successfully compromised, and it does not indicate how many sites or forms are being targeted overall. The CNA technical notice in the CVE record, as reviewed, does not report exploitation. The reviewed sources do not establish successful compromise or independent confirmation of exploitation.
Actions
- Confirm the plugin slug subscribe2, the installed version, and whether the popup-style subscription form is enabled.
- Back up and check compatibility, then update to the 10.48 patched release or a newer patched release.
- After updating, test signup, confirmation emails and the admin Subscribers list.
- Review subscriber entries and recent admin changes for anything unexpected and preserve logs; patching does not prove the site was clean.
- If the update must wait, ask your provider to assess restricting the affected public form, weighing business impact; this is a mitigation, not a guaranteed fix.
Unknowns
- Whether a given site was compromised before patching.
- The actual subscription form configuration on a given site.
- Whether any attempt against this flaw succeeded, and the extent of activity beyond what Wordfence observed and blocked; the reviewed sources do not establish successful compromise or independent confirmation.
- The overall scale of attack activity, because the Wordfence report reflects only its own rolling telemetry and not a complete count.
Sources
- Wordfence Intelligence https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/subscribe2/subscribe2-form-email-subscribers-newsletters-1047-unauthenticated-stored-cross-site-scripting-via-dataip-parameter
- Wordfence / CVE Program https://cveawg.mitre.org/api/cve/CVE-2026-120531
- Subscribe2 / WordPress Plugin Repository https://plugins.svn.wordpress.org/subscribe2/trunk/readme.txt
Change history
- — Published: Published 8 November 2026 based on the 7 November 2026 Wordfence advisory and CVE record; the vendor fix in 10.48 had already been available since September 2026.
- — Updated: Updated 9 November 2026: Wordfence now reports that its firewall blocked attack attempts targeting CVE-2026-120531 in the preceding 24 hours. This is vendor-reported blocked activity; the reviewed sources do not establish successful compromise or independent confirmation. Affected versions, the 10.48 patched release and the recommended actions are unchanged.