Skip to main content

AcyMailing SMTP Newsletter CVE-2026-94389

| EUVDEUVD-2026-89844 CRITICAL
Code Injection (CWE-94)
2026-09-30 Patchstack GHSA-hh4p-grc7-5x2c
9.0
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Identify site running AcyMailing SMTP Newsletter ≤11.0.5
  2. Delivery
    Send crafted unauthenticated request
  3. Exploit
    Trigger PHP code injection (CWE-94)
  4. Execution
    Execute arbitrary code on web server
  5. Impact
    Compromise host and beyond scope

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

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

Exploitation Conditions

Exploitation targets WordPress installations with the AcyMailing SMTP Newsletter plugin at version 11.0.5 or earlier installed and active. Per CVSS the attack is remote and unauthenticated with no user interaction (AV:N/PR:N/UI:N), so no account or victim click is required; however, AC:H signals a real limiting factor - reliable exploitation likely depends on a specific precondition, application state, or configuration/timing that the attacker must arrange or wait for, rather than a straightforward single request. The primary limits on real-world risk are therefore: the plugin must be present and within the vulnerable version range, and the attacker must overcome the high attack-complexity condition; there is no public PoC referenced to lower that barrier at this time.

Impact

This is a genuinely high-priority issue on paper: CVSS 3.1 base 9.0 driven by AV:N/PR:N/UI:N (remote, unauthenticated, no user interaction), S:C (scope change), and full C:H/I:H/A:H impact - consistent with unauthenticated RCE in a WordPress plugin (CWE-94 code injection). The single moderating signal in the vector is AC:H, indicating the exploit is not trivially fire-and-forget and likely requires meeting specific timing, state, or configuration conditions. However, real-world exploitation signals are thin: there is no EPSS score provided, no CISA KEV listing, and no public proof-of-concept referenced - the only source is a single Patchstack advisory, so this reflects 'no public exploit identified at time of analysis' rather than confirmed active exploitation. The AC:H versus otherwise-critical profile is worth verifying: unauthenticated RCE in a mail-sending plugin is highly attractive to opportunistic attackers, and if a working exploit becomes public the AC:H barrier may fall quickly. Net: treat as a real priority for anyone running the affected plugin and patch promptly, but current evidence points to potential rather than observed mass exploitation. Note the description asserts RCE while the vector's S:C/C:H/I:H/A:H is directionally consistent, but the exact code-injection sink is not disclosed in the provided data - verify specifics with the Patchstack advisory.

Exploit ScenarioDerived

A remote attacker without any account sends a specially crafted request to a WordPress site running AcyMailing SMTP Newsletter <= 11.0.5, triggering the code-injection flaw (CWE-94) to execute arbitrary PHP on the server. Because the attack is unauthenticated (PR:N) with no user interaction (UI:N) but rated AC:H, the attacker likely must satisfy a specific precondition or timing/state requirement to reliably land execution. No public PoC is referenced, so exploitation would currently require independent development.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.6% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 30, 2026

Unauthenticated remote code execution in the AcyMailing SMTP Newsletter WordPress plugin (versions 11.0.5 and earlier) allows a remote attacker to execute arbitrary code on the underlying server, leading to full site compromise. The CVSS 3.1 base score is 9.0 (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H), indicating no authentication or user interaction is required, though the high attack complexity (AC:H) signals that reliable exploitation likely depends on a specific precondition, application state, or configuration that the attacker must arrange or wait for. No public exploit code is currently identified, and the vulnerability is not listed in CISA KEV.

RemediationAI

No vendor-released patch version is identified in the provided intelligence. Administrators should immediately check the Patchstack advisory for an updated version and, until a fix is confirmed, deactivate and remove the AcyMailing SMTP Newsletter plugin from all WordPress installations. If the plugin must remain active for business reasons, apply virtual patching through a Web Application Firewall (WAF) that blocks code injection attempts targeting the plugin's endpoints, understanding that WAF rules may not cover all exploitation paths. Additionally, restrict access to the plugin's files and directories using server-level rules (e.g., disable PHP execution in the plugin folder) as a compensating control, though this is not a complete fix and will disable the plugin's functionality. Monitor logs for suspicious requests to the plugin's files. Trade-offs: deactivating the plugin disables newsletter and SMTP functionality; WAF and file restriction mitigations may be bypassed and require ongoing tuning. Consult the vendor advisory for definitive patching guidance.

Affected VersionsENISA

AcyMailing SMTP Newsletter n/a ≤11.0.5

Affected Packages

euvd acymailing_smtp_newsletter no fix

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 is a code injection (CWE-94) in the AcyMailing SMTP Newsletter plugin for WordPress. CWE-94 occurs when software constructs code segments using externally influenced input without properly neutralizing it, allowing an attacker to inject and execute arbitrary code. In this WordPress plugin context, the flaw likely resides in a feature that dynamically generates or evaluates PHP code based on user-supplied data-such as SMTP configuration settings, newsletter templates, or AJAX actions-without adequate sanitization. The CPE string cpe:2.3:a:acymailing_newsletter_team:acymailing_smtp_newsletter identifies the affected component; all versions up to and including 11.0.5 are vulnerable. The CVSS vector's S:C (scope change) indicates the exploit can affect resources beyond the vulnerable component's security scope, meaning a successful attack can compromise the entire WordPress installation and potentially the hosting environment. The AC:H metric reflects that exploitation likely requires the attacker to arrange a specific state or configuration, rather than a straightforward single request.

Know when Acymailing Smtp Newsletter 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 (Patchstack) PRIMARY 9.0 CRITICAL
AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 9.0 CRITICAL

Remote unauthenticated code injection (AV:N/PR:N/UI:N) yielding full RCE (C/I/A:H); AC:H reflects the disclosed high-complexity precondition, and S:C reflects code execution escaping the application's control.

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

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

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

DescriptionCVE.org

Unauthenticated Remote Code Execution (RCE) in AcyMailing SMTP Newsletter <= 11.0.5 versions.

Executive ViewAI

Why It Matters

A critical remote code execution flaw in the AcyMailing SMTP Newsletter plugin for WordPress (versions 11.0.5 and earlier) could allow an unauthenticated attacker to run arbitrary code on the web server hosting the affected site, placing any organization running that plugin at risk of full site and potentially broader infrastructure compromise. Because no vendor patch has been released and no public exploit code is currently identified, the near-term exposure is governed by how quickly teams can inventory, contain, or remove the affected plugin rather than by a routine patch cycle. Leadership should treat this as an active remediation project affecting any business unit or customer-facing property built on WordPress with this plugin installed.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or uninstall the AcyMailing plugin where feasible; if it must remain, block external access to its endpoints via WAF or reverse proxy rules, restrict wp-admin by IP allowlist with MFA, apply least-privilege file permissions, monitor for webshells and unauthorized changes, and maintain offline backups for rapid recovery.

Threat Intelligence Overview

EPSS Score
0.6%
Top 52% exploitable
Prevalence
Medium
AcyMailing is a widely-used WordPress newsletter plugin, though this SMTP variant is narrower
Data Quality
3 sources
Confidence: Low

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 CRITICAL
CISA KEV No
Public POC No
EPSS 0.6%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +45
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

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