<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>AcyMailing (&lt;= 11.1.0) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/acymailing--11.1.0/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 13 Oct 2026 08:34:05 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/acymailing--11.1.0/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Stored Cross-Site Scripting in AcyMailing WordPress Plugin</title><link>https://feed.craftedsignal.io/briefs/2026-10-acymailing-xss/</link><pubDate>Tue, 13 Oct 2026 08:34:05 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-acymailing-xss/</guid><description>An unauthenticated stored XSS vulnerability in AcyMailing WordPress plugin version 11.1.0 and earlier allows attackers to inject malicious scripts via the customField[] parameter.</description><content:encoded><![CDATA[<p>The AcyMailing plugin for WordPress, in versions up to and including 11.1.0, contains a critical security vulnerability involving Stored Cross-Site Scripting (XSS). The issue stems from insufficient input sanitization within the acym_cleanVar() function. Specifically, the plugin's HTML tag stripping mechanism is flawed, as it only successfully sanitizes complete tags that include a closing bracket. Furthermore, the SubscriberInsertion::replaceUserInformation() method and the archive view template fail to perform proper HTML encoding when substituting stored subscriber data into emails and archive pages. An unauthenticated attacker can exploit this by submitting malicious scripts through the customField[] parameter in the frontusers::subscribe endpoint. These scripts remain dormant until a victim, such as a site administrator, views the poisoned subscriber profile via the online-archive URL or the Subscribers history interface, at which point the script executes within the context of the victim's session.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated attackers to execute arbitrary JavaScript in the browser of an authenticated administrator or user. This can lead to session hijacking, unauthorized administrative actions within the WordPress dashboard, or the exfiltration of sensitive site data. The vulnerability affects all WordPress installations utilizing AcyMailing version 11.1.0 or lower.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Update the AcyMailing plugin to the latest version immediately to receive the patch for CVE-2026-102562.</li>
<li>Implement a Web Application Firewall (WAF) to filter incoming HTTP requests containing suspicious script tags or JavaScript event handlers in the customField[] parameter.</li>
<li>Audit the WordPress Subscribers history and archive pages for anomalous script tags if the site has been exposed to the internet while running vulnerable plugin versions.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>web-application</category><category>xss</category><category>cms</category><category>vulnerability</category></item></channel></rss>