<?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/"><channel><title>Auto Affiliate Links Plugin &lt;= 6.8.8 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/auto-affiliate-links-plugin--6.8.8/</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>Fri, 08 May 2026 09:16:10 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/auto-affiliate-links-plugin--6.8.8/feed.xml" rel="self" type="application/rss+xml"/><item><title>WordPress Auto Affiliate Links Plugin Stored XSS Vulnerability (CVE-2026-7330)</title><link>https://feed.craftedsignal.io/briefs/2026-05-wordpress-xss/</link><pubDate>Fri, 08 May 2026 09:16:10 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-wordpress-xss/</guid><description>The Auto Affiliate Links plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) in versions up to 6.8.8 due to insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary web scripts into the admin statistics page.</description><content:encoded><![CDATA[<p>The Auto Affiliate Links plugin, a WordPress plugin, is susceptible to a stored Cross-Site Scripting (XSS) vulnerability affecting versions up to and including 6.8.8. The vulnerability stems from a lack of proper input sanitization within the <code>aal_url_stats_save_action()</code> function when handling the &lsquo;url&rsquo; POST parameter. Additionally, there is a complete absence of output escaping in the <code>aal_display_clicks()</code> function, where user-supplied input is directly echoed into an anchor element&rsquo;s <code>href</code> attribute and inner text without applying <code>esc_url()</code>, <code>esc_attr()</code>, or <code>esc_html()</code>. Attackers can exploit this vulnerability without authentication by injecting malicious web scripts into the admin statistics page using a publicly exposed nonce and an unauthenticated AJAX endpoint registered through the <code>wp_ajax_nopriv_</code> hook. Successful exploitation results in the execution of arbitrary web scripts within an administrator&rsquo;s browser upon visiting the affected page.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An unauthenticated attacker crafts a malicious HTTP POST request to the WordPress site&rsquo;s AJAX endpoint (<code>wp-admin/admin-ajax.php</code>).</li>
<li>The POST request includes the <code>action</code> parameter set to <code>aal_url_stats_save_action</code> and a <code>url</code> parameter containing the XSS payload.</li>
<li>WordPress processes the AJAX request, invoking the <code>aal_url_stats_save_action()</code> function within the Auto Affiliate Links plugin.</li>
<li>The <code>aal_url_stats_save_action()</code> function fails to properly sanitize the <code>url</code> parameter, allowing the XSS payload to be stored in the WordPress database.</li>
<li>An administrator visits the admin statistics page, which calls the <code>aal_display_clicks()</code> function to display the stored URLs.</li>
<li>The <code>aal_display_clicks()</code> function retrieves the unsanitized URL containing the XSS payload from the database.</li>
<li>The XSS payload is echoed directly into the <code>href</code> attribute and inner text of an anchor element without proper escaping via <code>esc_url()</code>, <code>esc_attr()</code>, or <code>esc_html()</code>.</li>
<li>The administrator&rsquo;s browser executes the injected XSS payload, potentially leading to account compromise or further malicious actions.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this stored XSS vulnerability can allow an unauthenticated attacker to execute arbitrary JavaScript code in the context of an administrator&rsquo;s browser. This could lead to a variety of malicious activities, including account takeover, defacement of the WordPress site, or redirection of users to malicious websites. Given the lack of authentication required for the initial injection, the vulnerability poses a significant risk to websites using the affected plugin.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the Auto Affiliate Links plugin to the latest version, which includes a fix for CVE-2026-7330.</li>
<li>Deploy the Sigma rule &ldquo;Detect WordPress Auto Affiliate Links Plugin XSS Attempt&rdquo; to identify potential exploitation attempts by monitoring POST requests with suspicious characters in the <code>url</code> parameter.</li>
<li>Implement proper input sanitization and output escaping techniques in all WordPress plugins to prevent similar XSS vulnerabilities.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>wordpress</category><category>xss</category><category>plugin</category></item></channel></rss>