<?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>Independent Analytics (&lt;= 2.15.0) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/independent-analytics--2.15.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>Wed, 05 Aug 2026 15:20:48 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/independent-analytics--2.15.0/feed.xml" rel="self" type="application/rss+xml"/><item><title>Stored Cross-Site Scripting in Independent Analytics Plugin for WordPress</title><link>https://feed.craftedsignal.io/briefs/2026-08-cve-2026-17506-xss/</link><pubDate>Wed, 05 Aug 2026 15:20:48 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-cve-2026-17506-xss/</guid><description>The Independent Analytics plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'not_found_url' parameter, allowing unauthenticated attackers to execute arbitrary scripts in the context of victim browsers.</description><content:encoded><![CDATA[<p>The Independent Analytics plugin for WordPress (versions 2.15.0 and earlier) contains a high-severity Stored Cross-Site Scripting (XSS) vulnerability, identified as CVE-2026-17506. The vulnerability stems from improper sanitization logic within the plugin's reporting functionality. Specifically, the get_cell_content() function applies a urldecode() operation after the initial esc_url() sanitization. This sequence permits percent-encoded HTML tags to bypass URL validation filters. Once decoded, the raw markup is rendered within the plugin's admin reporting interface.</p>
<p>The flaw is exacerbated by the plugin's public REST endpoint, /iawp/search, which accepts unauthenticated requests. An attacker can leverage this to inject malicious payloads into the 404 tracking parameter. Because wp_kses_post() filtering allows certain img elements and data-* attributes, malicious payloads can persist in the database. When an administrator or authenticated user views the 404 report page, the injected script executes in their browser, potentially leading to unauthorized actions or credential theft.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated attackers to inject persistent malicious scripts into the WordPress site's reporting dashboard. This primarily threatens administrative accounts viewing the 404 URL column within the Independent Analytics plugin. Impact includes potential session hijacking, unauthorized administrative actions, and redirection of site users, affecting any WordPress installation using the vulnerable versions of this plugin.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Update the Independent Analytics plugin to the latest version immediately to remediate CVE-2026-17506.</li>
<li>Audit access logs for anomalous POST requests directed at the /iawp/search endpoint.</li>
<li>Deploy web application firewall (WAF) rules to inspect the 'not_found_url' parameter for percent-encoded HTML characters or suspicious JavaScript patterns.</li>
<li>Restrict access to WordPress administrative dashboards and sensitive REST API endpoints to trusted IP addresses.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>