EUVD-2026-12841Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious payload in 'event_type' parameter
-
DeliverySubmit request to vulnerable Post SMTP plugin
-
ExploitStored XSS executed in user session
-
ExecutionSteal session tokens or credentials
-
ImpactRedirect users to phishing site
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 | Unauthenticated remote attacker exploits Stored XSS via 'event_type' parameter in Post SMTP plugin versions ≤3.8.0. Requires Post SMTP Pro plugin with Reporting and Tracking extension installed. No victim interaction needed; payload executes when any user accesses injected page. |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N) indicates network-accessible exploitation with low complexity requiring no privileges or user interaction, with changed scope and low confidentiality and integrity impact. While the 7.2 score suggests high severity, real-world risk is moderated by the conditional requirement that both Post SMTP free and Pro plugins must be installed with specific extensions enabled, significantly reducing the potential victim pool. The unauthenticated attack vector is concerning as it allows external attackers to inject persistent malicious scripts without authentication. No EPSS score or KEV listing is provided in the intelligence, suggesting this is not currently observed in active exploitation. A patch is available as evidenced by the Trac changeset 3484515, and the specific vulnerable code location has been identified at line 459 of PostmanEmailLogs.php. Organizations using both the free and Pro versions should prioritize patching, while sites using only the free version without Pro extensions face no immediate risk from this specific vulnerability. |
| Exploit ScenarioDerived | An unauthenticated attacker crafts a malicious HTTP request to a WordPress site running both Post SMTP free and Pro plugins with the Reporting and Tracking extension enabled, injecting JavaScript code through the 'event_type' parameter. The malicious script is stored in the database and executes in the browser of any administrator or user who subsequently views the email logs or tracking reports, potentially allowing the attacker to steal session cookies, perform actions as the victim user, or further compromise the WordPress installation. Given the low attack complexity and no authentication requirement (PR:N/UI:N), exploitation can be automated and executed remotely without requiring social engineering or legitimate credentials. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 18, 2026
A stored cross-site scripting (XSS) vulnerability exists in the Post SMTP WordPress plugin through version 3.8.0, allowing unauthenticated attackers to inject malicious scripts via the 'event_type' parameter. The vulnerability requires the Post SMTP Pro plugin with its Reporting and Tracking extension to be enabled for exploitation. With a CVSS score of 7.2 and unauthenticated network-based exploitation possible, this represents a moderate-to-high severity risk for WordPress sites using both the free and Pro versions of Post SMTP together.
RemediationAI
Upgrade the Post SMTP plugin to version 3.8.1 or later, which addresses the input sanitization issue in the 'event_type' parameter as documented in changeset 3484515 available at https://plugins.trac.wordpress.org/changeset/3484515/. Site administrators should update through the WordPress plugin management interface or manually download the patched version from the official WordPress plugin repository. Until patching is completed, temporary mitigation can be achieved by disabling the Reporting and Tracking extension in the Post SMTP Pro plugin settings, which removes the exploitable attack surface, or by implementing Web Application Firewall rules to filter malicious input to the 'event_type' parameter. Review existing email logs and tracking data for suspicious script content that may have been injected prior to patching, and consider implementing Content Security Policy headers to limit the impact of any residual XSS payloads.
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 vulnerability affects Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App (CPE: cpe:2.3:a:saadiqbal:post_smtp_–_complete_email_deliverability_and_smtp_solution_with_email_logs,_alerts,_backup_smtp_&_mobile_app:*:*:*:*:*:*:*:*), a WordPress plugin that handles email delivery via SMTP. The root cause is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically in the PostmanEmailLogs.php file at line 459 where the 'event_type' parameter is processed without adequate sanitization before being output to the page. This allows untrusted user input to be stored in the database and later rendered as executable JavaScript when administrators or users view the affected pages, creating a persistent XSS condition. The vulnerability is conditional on the Post SMTP Pro plugin being installed with its Reporting and Tracking extension enabled, limiting the attack surface to sites using both the free and premium versions simultaneously.
Know when Wordpress Plugin 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:N/S:C/C:L/I:L/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
DescriptionCVE.org
The Post SMTP - Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘event_type’ parameter in all versions up to, and including, 3.8.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability is only exploitable when the Post SMTP Pro plugin is also installed and its Reporting and Tracking extension is enabled.
Executive ViewAI
A stored cross-site scripting vulnerability in the Post SMTP WordPress plugin allows unauthenticated attackers to inject malicious scripts into affected websites. Organizations using both the free Post SMTP plugin and Pro version with Reporting and Tracking enabled face immediate risk of website defacement, credential theft, and malware distribution to site visitors.
Implement Web Application Firewall (WAF) rules to filter malicious input to the 'event_type' parameter; disable the Post SMTP Pro Reporting and Tracking extension to remove exploitation vector; restrict plugin access to authenticated users only via access controls; apply Content Security Policy (CSP) headers to mitigate XSS payload execution; consider network segmentation to isolate affected WordPress instances; monitor application logs for suspicious 'event_type' parameter submissions; evaluate alternative SMTP plugins as replacement solution pending vendor patch availability.
Threat Intelligence Overview
NVD
CVE.org
EPSS
VulDB
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.
Related Vulnerabilities in Post SMTP WordPress Plugin XSS Vulnerabilities
View all 2More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
GitHub PoC
Exploit-DB