CVE-2026-12170: AcyMailing WordPress Plugin Stored XSS Vulnerability (CVSS 6.4)
AcyMailing, a popular WordPress newsletter and marketing automation plugin, contains a stored cross-site scripting (XSS) flaw in its 'alignment' attribute handler. Authenticated WordPress contributors and higher-privileged users can inject malicious scripts that persist in the database and execute in the browsers of anyone viewing the affected pages. This affects all versions up to and including 10.10.2.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 6.4 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
- Weaknesses (CWE)
- CWE-79
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-09 / 2026-07-09
NVD description (verbatim)
The AcyMailing – An Ultimate Newsletter Plugin and Marketing Automation Solution for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'alignment' attribute in all versions up to, and including, 10.10.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
6 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-12170 is a Stored XSS vulnerability (CWE-79) in the AcyMailing WordPress plugin stemming from insufficient input sanitization and output escaping of the 'alignment' attribute. The vulnerability requires authenticated access at contributor level or above and has a network attack vector with no user interaction required on the attacker's part (though the payload executes when victims visit the page). The CVSS v3.1 score of 6.4 (Medium) reflects the broad scope impact across the WordPress site context.
Business impact
Organizations using AcyMailing for email campaigns and marketing automation face injection of arbitrary content into their newsletter pages and campaign materials. Compromised pages could redirect users, capture credentials, deface brand messaging, or distribute malware to subscribers—damaging reputation and customer trust. The attack is particularly insidious because it leverages legitimate contributor accounts, making detection harder than external compromises.
Affected systems
AcyMailing plugin for WordPress, all versions up to and including 10.10.2. The vulnerability is triggered through the plugin's handling of the 'alignment' attribute, suggesting it may affect email template creation, newsletter design, or related form/content configuration interfaces where this attribute is processed.
Exploitability
Exploitation requires prior authentication as a WordPress contributor, editor, or administrator. No additional complexity or user interaction is needed beyond the initial malicious input submission. While the attack surface is limited to authenticated insiders or compromised contributor accounts, the persistence of the payload (stored XSS) makes it a high-value target for attackers seeking sustained access and broad victim reach.
Remediation
Update AcyMailing to a patched version released after 10.10.2. Verify the exact version number in the official plugin repository or vendor advisory. As an interim control, restrict contributor-level access to only trusted staff and monitor database changes for suspicious alignment attribute values. Consider using WordPress security plugins to detect stored XSS patterns in post metadata.
Patch guidance
Check the AcyMailing official repository and vendor security advisories for the version that addresses CVE-2026-12170. Update through the WordPress admin dashboard or manually via SFTP once a patched release is confirmed. Test the update in a staging environment first, especially if you have custom newsletter templates or integrations. Verify that existing email campaigns and templates render correctly post-patch.
Detection guidance
Monitor WordPress database logs and post revision history for unexpected changes to post meta fields containing 'alignment' attributes with script-like content (e.g., <script, onerror=, onclick=). Use WordPress security scanners to audit plugin versions. Review contributor and editor user activity logs for unusual content modifications. Inspect the raw HTML of published newsletters and campaign pages for unescaped JavaScript or event handlers.
Why prioritize this
Although this is a Medium-severity vulnerability, its stored nature, broad impact across WordPress site scope, and reliance on an internal threat actor (compromised or malicious contributor) make it a meaningful risk in multi-user WordPress environments. Organizations with many contributors or weak access controls should prioritize patching. Those with mature contributor vetting and activity monitoring may deprioritize slightly, but should not ignore it.
Risk score, explained
The CVSS 6.4 score reflects: network-accessible WordPress admin/frontend, low attack complexity (straightforward XSS injection), requirement for authenticated access (reduces risk vs. unauthenticated), low confidentiality/integrity impact per-user, but changed scope (XSS can affect site-wide resources and other users). Not exploited in the wild (KEV status: false) and not linked to ransomware, which moderates urgency but does not eliminate the security debt.
Frequently asked questions
Could an unauthenticated attacker exploit this?
No. The vulnerability requires authentication at contributor level or higher in WordPress. However, if an attacker compromises a contributor account—or if your organization has loose access controls—they can exploit it.
Is this vulnerability actively exploited in the wild?
CVE-2026-12170 is not currently listed in the CISA KEV catalog, indicating no active exploitation in the wild as of the publication date. Nonetheless, stored XSS flaws are well-understood attack vectors and patching should not be deferred indefinitely.
What happens if we don't patch immediately?
An internal threat actor or compromised contributor could inject persistent malicious scripts into your newsletters and web pages. Victims would be silently affected whenever they visit those pages, risking credential theft, malware delivery, or brand damage. The longer you delay, the greater the exposure window.
Does this affect all WordPress installations using AcyMailing?
Yes, if you use AcyMailing version 10.10.2 or earlier, you are vulnerable. Even if no contributor-level accounts have been compromised, the vulnerability exists and should be remediated to reduce attack surface.
This analysis is based on publicly available vulnerability data as of the publication date. Patch version numbers, vendor advisory links, and specific remediation steps should be verified against the official AcyMailing repository and security advisories before implementation. SEC.co does not endorse or warrant the accuracy of third-party vendor statements. Organizations should conduct their own risk assessment and testing in controlled environments before deploying patches to production. No exploit code or weaponized proof-of-concept details are provided; responsible disclosure practices are assumed. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2016-20070MEDIUMPrivilege Escalation & Stored XSS in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2018-25384MEDIUMStored XSS in Wikidforum 2.20 Allows Authenticated Attackers to Inject Malicious Scripts
- CVE-2019-25731MEDIUMStored XSS in Zuz Music 2.1 Contact Form
- CVE-2019-25737MEDIUMStored XSS in Live Chat Unlimited 2.8.3 – Admin Session Compromise
- CVE-2019-25739MEDIUMGigToDo 1.3 Stored XSS Vulnerability in Proposal Descriptions
- CVE-2019-25742MEDIUMStored XSS in Zoner Real Estate WordPress Theme 4.1.1 – Admin Account Compromise Risk
- CVE-2019-25743MEDIUMWordPress Soliloquy Lite 2.5.6 Stored XSS Vulnerability
- CVE-2019-25744MEDIUMWordPress Popup Builder 3.49 Stored XSS Vulnerability – Exploit Prevention & Patch Guide