Skip to main content

Subscribe2 CVE-2026-14331

| EUVDEUVD-2026-54376 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-08-07 WPScan GHSA-m3cj-4969-qh2q
6.1
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft malicious Subscribe2 form URL with XSS payload
  2. Delivery
    Deliver link via phishing email or social media
  3. Exploit
    Victim clicks link, loads vulnerable subscription form
  4. Execution
    Server reflects unsanitized parameter into HTML response
  5. Persist
    Browser executes injected JavaScript in site's origin context
  6. Impact
    Attacker exfiltrates session token or redirects victim to phishing page

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The Subscribe2 WordPress plugin must be installed, active, and at a version earlier than 10.46 on the target site. The plugin's public subscription form must be reachable by unauthenticated users (the default configuration). The attacker requires no authentication on the WordPress site (PR:N per CVSS vector). The critical limiting factor is mandatory victim interaction: the victim must click a specifically crafted URL and load the subscription form page - passive or drive-by exploitation without user action is not possible (UI:R per CVSS vector). Exploitation is further constrained to the victim's browser session; there is no server-side code execution or database access involved. Sites that have restricted subscription form access to authenticated users only, or that have disabled the Subscribe2 frontend form, are not exploitable.

Impact

CVSS 6.1 (Medium) is consistent with the attack profile: network-reachable (AV:N), low complexity (AC:L), no attacker privileges (PR:N), but requiring victim interaction (UI:R) and constrained to low confidentiality and integrity impact (C:L/I:L) with no availability impact (A:N). The mandatory UI:R step is the primary real-world friction point - the attacker cannot exploit this passively and must deliver a crafted link via phishing or social engineering. The EPSS score of 0.16% at the 5th percentile corroborates this, suggesting exploitation is unlikely at scale. This is not a CISA KEV-listed vulnerability, so confirmed active exploitation is not established. However, a publicly available POC dramatically lowers the attacker skill bar, and WordPress plugins with wide deployment are frequent phishing campaign targets. Real-world priority is moderate: sites with high subscriber traffic or sensitive admin sessions are at elevated risk from targeted link-delivery attacks.

Exploit ScenarioDerived

An attacker identifies a WordPress site running a vulnerable Subscribe2 plugin version and constructs a URL to the public subscription form embedding a JavaScript payload in the vulnerable query parameter. The attacker distributes the link via a phishing email disguised as a newsletter confirmation or subscription invitation, targeting the site's existing subscriber base. When a recipient clicks the link and the form loads, the injected script executes in the victim's browser, allowing the attacker to exfiltrate session cookies, redirect the victim to a credential harvesting page, or silently perform authenticated actions if the victim is logged into WordPress. A public POC is available from WPScan, meaning this requires minimal attacker expertise to weaponize.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 07, 2026

Reflected XSS in the Subscribe2 WordPress plugin (versions before 10.46) allows an unauthenticated attacker to inject arbitrary JavaScript into a public subscription form by luring a visitor to a crafted link. Exploitation requires the victim to interact with the malicious URL - no server-side authentication is needed - enabling session theft, credential harvesting, or DOM-based actions scoped to the victim's browser. A publicly available proof-of-concept exists per WPScan; EPSS at 0.16% (5th percentile) indicates limited automated exploitation despite the low attack complexity.

RemediationAI

Update the Subscribe2 plugin to version 10.46 or later, which applies proper output escaping to the vulnerable subscription form parameter; this is the vendor-released patch confirmed by WPScan's advisory at https://wpscan.com/vulnerability/5ea58741-0c4c-4482-94dd-34721b19fc26/. WordPress site administrators can apply the update directly from the WordPress plugin dashboard. If an immediate upgrade is blocked, a compensating control is to temporarily deactivate the Subscribe2 plugin until patching is possible - this eliminates the attack surface entirely with no residual risk beyond loss of subscription functionality. Alternatively, a WAF rule blocking reflected parameter injection patterns in requests to the Subscribe2 form endpoint can reduce exposure, but WAF rules risk false positives on legitimate subscription submissions and should be validated in audit mode before enforcement. Do not rely solely on WAF mitigation; patch to 10.46 as the primary remediation.

Affected VersionsENISA

Subscribe2 0 <10.46

Affected Packages

euvd subscribe2 fix: 10.46

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Subscribe2 is a WordPress email subscription management plugin that renders a public-facing subscriber enrollment form. CWE-79 (Improper Neutralization of Input During Web Page Generation) identifies the root cause: one or more user-controlled query parameters are echoed directly into the form's HTML output without being HTML-entity-encoded or sanitized, allowing injected script payloads to execute in the victim's browser. The CVSS 3.1 vector assigns S:C (scope change), reflecting that the exploit crosses from the server-rendered WordPress page into the browser's JavaScript execution context - the canonical impact profile for reflected XSS. The CPE identifier cpe:2.3:a:unknown:subscribe2:*:*:*:*:*:*:*:* covers all versions through pre-10.46, with the vendor field unresolved in NVD but the plugin identity confirmed by WPScan and EUVD-2026-54376.

Know when Subscribe2 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 6.1 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
vuln.today AI 6.1 MEDIUM

Reflected XSS via crafted link mandates victim interaction (UI:R) and crosses into browser scope (S:C); no attacker privileges required and no server-side availability impact applies.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

4
CVSS changed
Aug 07, 2026 - 18:22 NVD
6.1 (MEDIUM)
Patch available
Aug 07, 2026 - 07:01 EUVD
CVE Published
Aug 07, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 07, 2026 - 06:00 cve.org
MEDIUM 6.1

DescriptionCVE.org

The Subscribe2 WordPress plugin before 10.46 does not properly escape a user-supplied value before reflecting it into a public subscription form, leading to Reflected Cross-Site Scripting that executes in the browser of an unauthenticated visitor who interacts with the form through a crafted link.

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Medium
popular WordPress email subscription plugin with broad install base
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

50
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy