<?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>Cpe:2.3:a:wordpress:paid_downloads:*:*:*:*:*:*:*:* - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3awordpresspaid_downloads/</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>Thu, 17 Sep 2026 05:55:08 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3awordpresspaid_downloads/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>Arbitrary File Upload Vulnerability in Paid Downloads WordPress Plugin</title><link>https://feed.craftedsignal.io/briefs/2026-09-cve-2026-87935-wp-plugin/</link><pubDate>Thu, 17 Sep 2026 05:55:08 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-cve-2026-87935-wp-plugin/</guid><description>An unauthenticated arbitrary file upload vulnerability in the Paid Downloads plugin (&lt;= 3.15) allows remote attackers to execute code by bypassing file type validation via the admin_request_handler function.</description><content:encoded><![CDATA[<p>The Paid Downloads plugin for WordPress, in all versions up to and including 3.15, contains a critical arbitrary file upload vulnerability. The flaw resides in the admin_request_handler function, which fails to implement necessary authorization checks or file type validation. Because the function is reachable via an unauthenticated request to /wp-admin/admin-post.php, an attacker can upload arbitrary files, including executable scripts, to the web server.</p>
<p>This vulnerability primarily impacts environments where the web server does not honor .htaccess files or where such directives are disabled, including nginx, LiteSpeed, and Apache configurations with 'AllowOverride None'. Successful exploitation grants the attacker the ability to achieve remote code execution on the underlying server. Defenders should focus on monitoring for unauthorized file uploads in the plugin directory and unexpected requests directed at the admin-post.php endpoint.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows an unauthenticated remote attacker to gain remote code execution capabilities on the host server. This impact is significant for any WordPress installation utilizing the Paid Downloads plugin, as it could lead to full site compromise, exfiltration of sensitive database content, and further lateral movement within the network. The scope includes any server running the vulnerable versions of the plugin on web server software that does not restrict file execution via .htaccess.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Prioritize updating the Paid Downloads plugin to the latest secure version immediately. If an update is not available, temporarily disable the plugin until a patch is applied.</p>
<ul>
<li>Monitor web access logs for anomalous POST requests to /wp-admin/admin-post.php.</li>
<li>Audit the file system for recently uploaded executable files (e.g., .php files) within the plugin upload directories.</li>
<li>Implement strict file-type and size limitations on web server configurations.</li>
<li>Utilize the Sigma rule provided below to detect potential exploitation attempts.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>web-vulnerability</category><category>wordpress</category><category>remote-code-execution</category></item></channel></rss>