<?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>AMP for WP – Accelerated Mobile Pages (&lt;= 1.1.16) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/amp-for-wp--accelerated-mobile-pages--1.1.16/</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, 25 Sep 2026 10:52:07 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/amp-for-wp--accelerated-mobile-pages--1.1.16/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 XSS in AMP for WP WordPress Plugin</title><link>https://feed.craftedsignal.io/briefs/2026-09-cve-2026-83591/</link><pubDate>Fri, 25 Sep 2026 10:52:07 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-cve-2026-83591/</guid><description>The AMP for WP WordPress plugin is vulnerable to stored Cross-Site Scripting via insufficient sanitization of comment content, allowing unauthenticated attackers to execute arbitrary web scripts.</description><content:encoded><![CDATA[<p>The AMP for WP - Accelerated Mobile Pages plugin for WordPress, in all versions up to and including 1.1.16, contains a stored Cross-Site Scripting (XSS) vulnerability. The issue stems from inadequate input sanitization and output escaping when processing comment content. Specifically, the plugin uses a regex transformation pipeline that fails to filter the 'javascript:' protocol within anchor tag attributes. Because the AMP sanitizer pipeline permits anchor tags with 'href' and 'title' attributes - which are considered legitimate by standard WordPress comment filters - the malicious payload bypasses intended security controls. An unauthenticated attacker can submit a crafted comment containing a JavaScript-based URI, which is then stored and executed in the context of any user visiting the compromised page. This represents a significant risk for session hijacking, credential theft, or unauthorized actions performed on behalf of legitimate users.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated attackers to execute arbitrary JavaScript in the context of a user's session. This can lead to full account compromise if the victim is an administrator, modification of page content, or redirection to malicious sites. The vulnerability affects all WordPress instances using the AMP for WP plugin up to version 1.1.16.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Prioritize the immediate update of the AMP for WP - Accelerated Mobile Pages plugin to a version addressing this flaw. In the absence of an available patch, consider disabling comment functionality on AMP-enabled pages or implementing a Web Application Firewall (WAF) rule to block common XSS patterns including 'javascript:' pseudo-protocols in user-supplied content. Detection engineers should monitor web server logs for HTTP POST requests directed at comment submission endpoints that contain suspicious anchor tag attributes or URI schemes.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>web-application</category><category>xss</category><category>wordpress</category></item></channel></rss>