Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious XSS payload
-
DeliveryDeliver crafted link to WordPress user
-
ExploitVictim browser renders unsanitized input
-
ExecutionScript executes in victim session
-
ImpactHijack session or perform actions
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 | Exploitation requires the attacker to get a WordPress user to interact with attacker-controlled content (UI:R) - for example clicking a crafted link or loading a page that renders the injected payload - on a site running WP Mailster version 1.9.0.0 or earlier. No authentication is required (PR:N), so any unauthenticated remote attacker can attempt it, but success is LIMITED by the mandatory user-interaction step and by the site actually having the vulnerable plugin installed and the affected feature exposed. The description does not name a specific parameter, feature toggle, or non-default configuration, so the precise injection point is not specified in the available data. |
| Impact | This is a moderate-severity reflected/stored Cross-Site Scripting flaw (CWE-79) with a CVSS 3.1 base score of 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L). The network vector, low attack complexity, and no required privileges (PR:N, unauthenticated) raise its theoretical reach, but the requirement for user interaction (UI:R) means an attacker must lure or wait for a victim to trigger the payload, which meaningfully lowers real-world exploitability versus a no-interaction bug. The scope change (S:C) reflects that injected script executes in the victim's browser context, impacting resources beyond the vulnerable component. No EPSS score was supplied, the CVE is NOT listed in CISA KEV, and no public proof-of-concept is referenced - so there is no public exploit identified at time of analysis and no evidence of active exploitation. The only intelligence source is Patchstack (also mirrored to CVE.org and ENISA EUVD), with no independent vendor advisory confirming patch status. Net assessment: a legitimate but not urgent issue - a classic high-CVSS XSS whose real risk is tempered by required user interaction, absence of exploitation signals, and the limited footprint of the affected plugin; prioritize routine patching rather than emergency response. |
| Exploit ScenarioDerived | An unauthenticated attacker crafts a malicious URL or input containing JavaScript targeting a vulnerable parameter in WP Mailster <= 1.9.0.0 and delivers it to a WordPress user (e.g., via phishing or a planted link). When the victim's browser renders the unsanitized output, the script executes in their session context, enabling session/cookie theft or actions on their behalf. No public exploit code is referenced, and successful exploitation depends on the victim interacting with the attacker-supplied content (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Cross-site scripting in the WP Mailster WordPress plugin (all versions up to and including 1.9.0.0) allows an unauthenticated remote attacker to inject script content that executes in the browser of a victim WordPress user, enabling session hijacking, content tampering, redirection to malicious sites, or actions performed with the victim's privileges. Exploitation is not automatic: the attacker must induce a user to click a crafted link or load a page that renders the injected payload (CVSS UI:R), and the target must actually be running the vulnerable plugin, though no attacker authentication is required (PR:N). 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), no public exploit code has been identified at time of analysis, and the flaw is tracked as CWE-79 with an EUVD record (EUVD-2026-93086) and a Patchstack-issued advisory.
RemediationAI
No vendor-released patch version is identified in the available data; consult the Patchstack advisory for WP Mailster (https://patchstack.com/database/wordpress/plugin/wp-mailster/vulnerability/wordpress-wp-mailster-plugin-1-9-0-0-cross-site-scripting-xss-vulnerability) to confirm whether a fixed release has been published and to obtain the exact patched version before upgrading. Until a patched release is verified, the most reliable compensating control is to deactivate and delete the WP Mailster plugin if mailing-list functionality is not required on the site - this removes the attack surface entirely at the cost of losing subscription/newsletter features. If the plugin must remain active, deploy a Web Application Firewall with XSS signatures as a virtual patch in front of WordPress and restrict or rate-limit access to the plugin's public-facing endpoints and form submissions, accepting that signature-based filtering can be bypassed by encoding and obfuscation techniques. Because WordPress plugin auto-updates are disabled by default on many managed hosts, manually verify the installed WP Mailster version, enable auto-updates where policy permits, and re-check the advisory for a fixed release. Additionally, enforce a Content-Security-Policy that blocks inline and third-party script execution to reduce the impact of any successful injection (a control that frequently breaks legitimate site scripts and requires staging/testing), and ensure WordPress authentication cookies carry the HttpOnly and Secure attributes to limit session theft if script execution does occur.
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
The issue is a classic CWE-79 improper neutralization of input during web page generation (cross-site scripting) in the WP Mailster WordPress plugin. The plugin fails to sufficiently encode or sanitize attacker-controllable input before reflecting/rendering it in an HTML response, so browser-side JavaScript executes in the security context of the affected site. The CVSS vector's scope-changed (S:C) rating reflects that the injected script runs in the victim's browser session and can therefore affect resources beyond the vulnerable plugin itself - for example authenticated WordPress admin sessions or other content on the same origin - while the low integrity/confidentiality/availability impacts (C:L/I:L/A:L) indicate script-level effects rather than server compromise. The supplied CPE string (cpe:2.3:a:bởi_brandtoss:wp_mailster:*:*:*:*:*:*:*:*) identifies the affected package as the WP Mailster plugin under the vendor namespace recorded by the CPE source, and the EUVD record lists all WP Mailster versions up to and including 1.9.0.0 as vulnerable. Notably, the available data does not identify the specific parameter, form field, or non-default configuration that serves as the injection point, and it does not distinguish conclusively between reflected and stored XSS delivery, so the exact trigger path should be confirmed against the Patchstack advisory or by plugin source review before assuming a particular endpoint is exploitable.
Know when Wp Mailster 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 XSS (AV:N/PR:N) needing victim interaction (UI:R); script runs in browser context changing scope (S:C) with limited C/I/A impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Cross Site Scripting (XSS) in WP Mailster <= 1.9.0.0 versions.
Executive ViewAI
A high-severity cross-site scripting flaw affects every version of the WP Mailster plugin for WordPress up to and including 1.9.0.0, exposing any organization running that plugin on its public sites. Because the flaw can be triggered without attacker credentials, a crafted link clicked by a logged-in WordPress user - potentially an administrator - could let an outsider hijack that session and act with the victim's privileges. With no vendor patch yet available, leadership should treat this as an open exposure requiring immediate interim controls and a decision on whether the plugin can remain in production.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or uninstall the WP Mailster plugin until a fix is available; where the plugin must stay enabled, apply WAF or managed-host virtual patching rules for the affected request patterns, restrict administrative access to trusted networks, enforce multi-factor authentication and shorter session timeouts for WordPress users, and warn users not to follow unsolicited links while authenticated. Note that unauthenticated access is required to deliver the payload and the attacker must induce a user to click a crafted link (UI:R); no public exploit code has been identified at time of analysis.
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.
More in Wp Mailster
View allThe WP Mailster plugin before 1.5.5 for WordPress has XSS in the unsubscribe handler via the mes parameter to view/subsc
WP Mailster 1.6.18.0 allows XSS when a victim opens a mail server's details in the mst_servers page, for a crafted serve
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in brandtoss WP Mails
Insertion of Sensitive Information Into Sent Data vulnerability in brandtoss WP Mailster wp-mailster allows Retrieve Emb
Missing Authorization vulnerability in brandtoss WP Mailster wp-mailster allows Exploiting Incorrectly Configured Access
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in brandtoss WP Mails
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in brandtoss WP Mails
Missing Authorization vulnerability in brandtoss WP Mailster wp-mailster allows Exploiting Incorrectly Configured Access
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in brandtoss WP Mails
The WP Mailster plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'mst_subscribe' short
WP Mailster, a WordPress newsletter and mailing-list plugin, contains a missing authorization flaw (CWE-862) affecting a
Insertion of Sensitive Information Into Sent Data vulnerability in brandtoss WP Mailster allows Retrieve Embedded Sensit
EUVD-2026-93086
GHSA-2292-9q2v-h2m2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB