Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious URL to weMail AJAX endpoint
-
DeliveryLure authenticated admin to click link
-
ExploitUnescaped parameter reflected into HTML attribute
-
ExecutionInjected JavaScript executes in admin session
-
ImpactSteal session / create rogue admin account
Vulnerability Assessment
| Weakness |
CWE
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 | Exploitation requires the target site to run weMail below 2.1.3 and requires a victim who is already authenticated to WordPress (ideally an administrator) to click an attacker-crafted URL - the UI:R user-interaction requirement is the primary limiting factor. No attacker authentication is needed (PR:N, unauthenticated delivery), and the vulnerable AJAX response is not nonce-protected, so no valid CSRF token is required to reach the reflection. The attack is not automatable at scale (SSVC Automatable: no) precisely because it depends on social-engineering a logged-in user; impact is bounded by the privileges of whichever authenticated user opens the link. |
| Impact | Signals are mixed and point to a moderate, opportunistic risk rather than a top-priority emergency. The CVSS 3.1 base score is 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L): network-reachable, low complexity, no privileges, but requiring user interaction, with a scope change reflecting that injected script executes in the victim's authenticated session. SSVC aligns with this - Exploitation: poc, Automatable: no (because a victim must click a crafted link, so it cannot be mass-automated), Technical Impact: partial. EPSS is low at 0.21% (11th percentile) and the CVE is NOT on CISA KEV, indicating no confirmed widespread exploitation despite public POC. The practical priority driver is that the injected script runs against administrators, so a single successful lure can escalate to full site compromise. Net: a real but interaction-gated issue - patch promptly, but it is not a wormable, unauthenticated-RCE-class event. |
| Exploit ScenarioDerived | An attacker crafts a URL to the vulnerable, non-nonce-protected weMail AJAX endpoint with a malicious payload in the reflected parameter and delivers it to a logged-in WordPress administrator (via email, comment, or messaging). When the admin opens the link, the unescaped payload breaks out of the HTML attribute and executes JavaScript in their authenticated session, allowing the attacker to steal session cookies, create rogue admin accounts, or perform actions as the admin. Public exploit code from WPScan lowers the skill needed to reproduce this low-complexity, network-delivered attack. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 22, 2026
Reflected Cross-Site Scripting in the weMail WordPress plugin (versions before 2.1.3) lets unauthenticated attackers inject arbitrary JavaScript by luring any logged-in user to a crafted URL, because a user-supplied parameter is reflected unescaped into an HTML attribute on an AJAX endpoint that lacks nonce protection. Successful exploitation runs script in the victim's authenticated browser session - including administrators - enabling session/account takeover of the WordPress site. Publicly available exploit code exists (WPScan), though EPSS is low (0.21%) and there is no evidence of active exploitation.
RemediationAI
Update the weMail plugin to version 2.1.3 or later, which contains the vendor fix (Patch available per vendor advisory; exact patched release: 2.1.3). Because exploitation requires a victim to click a crafted URL, until you can patch you can reduce exposure by deploying a WAF rule to filter script/attribute-breakout payloads on the plugin's admin-ajax.php requests, and by advising administrators not to open unsolicited links to the site - noting these are stopgaps that do not remove the underlying unescaped-reflection flaw. Restricting or monitoring access to the vulnerable AJAX action helps but may break legitimate plugin functionality if the endpoint is used by normal workflows. Refer to the WPScan advisory (https://wpscan.com/vulnerability/f00c1853-a4b2-4e91-99b3-fed8acbe6da7/) for confirmation of the fixed version.
Affected VersionsENISA
Affected Packages
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
weMail is an email-marketing, automation and newsletter plugin for WordPress with WooCommerce integration, running as server-side PHP that registers AJAX handlers via WordPress's admin-ajax.php. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation): a request parameter is echoed into an HTML attribute context without output encoding. Two compounding weaknesses make this exploitable by unauthenticated actors: the AJAX response is not nonce-protected (no CSRF/request-origin validation) and the reflected value is not escaped for the attribute context (e.g., no esc_attr()), so an attacker can break out of the attribute and inject an event handler or script. The affected CPE is cpe:2.3:a:unknown:wemail:_email_marketing,_email_automation,_newsletters,_subscribers_&_email_optins_for_woocommerce, with the vulnerable code present in all releases prior to 2.1.3.
Know when Wemail 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
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Unauthenticated network delivery (PR:N/AV:N) but victim must click a crafted link (UI:R); reflected XSS runs in a different security context (S:C) with limited C/I/A impact.
Primary rating from CISA-ADP.
CVSS VectorCISA-ADP
Lifecycle Timeline
3DescriptionCVE.org
The weMail: Email Marketing, Email Automation, Newsletters, Subscribers & Email Optins for WooCommerce WordPress plugin before 2.1.3 does not properly escape a user-supplied parameter before reflecting it into an HTML attribute on a non-nonce-protected AJAX response, allowing unauthenticated attackers to deliver Reflected Cross-Site Scripting against any authenticated user (including administrators) via a crafted URL.
Executive ViewAI
The weMail WordPress plugin (versions before 2.1.3) contains a reflected cross-site scripting vulnerability with publicly available exploit code that allows attackers to inject malicious scripts and hijack administrator accounts through social engineering. Organizations using affected versions face potential unauthorized site access and data compromise. Although active exploitation has not been reported at this time, immediate patching to version 2.1.3 is required to secure WordPress installations.
Apply vendor patch: weMail 2.1.3 or later.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in weDevs weMail wema
Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in weDevs weMail allows Retriev
Missing Authorization vulnerability in weDevs weMail.14.2. Rated medium severity (CVSS 5.3), this vulnerability is remot
EUVD-2026-37557
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB