<?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>ACPT - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/acpt/</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, 04 Sep 2026 07:24:32 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/acpt/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>Unauthenticated Privilege Escalation in ACPT Premium Plugin</title><link>https://feed.craftedsignal.io/briefs/2026-09-acpt-privesc/</link><pubDate>Fri, 04 Sep 2026 07:24:32 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-acpt-privesc/</guid><description>The ACPT Premium WordPress plugin contains a critical authorization flaw in the submit() function, allowing unauthenticated attackers to hijack administrative accounts by overwriting credentials.</description><content:encoded><![CDATA[<p>The ACPT (Premium) plugin for WordPress is vulnerable to a critical privilege escalation vulnerability, assigned CVE-2026-15354, affecting all versions up to and including 2.0.66. The flaw exists within the plugin's <code>submit()</code> function, which fails to verify user authorization before executing account update operations. By interacting with a public-facing ACPT form, an unauthenticated attacker can manipulate the target user ID parameter passed to the <code>wp_update_user()</code> function. This allows the attacker to arbitrarily modify the email address and password of any registered user on the WordPress site. If the target is an administrator, this results in a full site takeover. Organizations using this plugin should immediately update to a patched version once available or disable public-facing forms managed by the plugin.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker identifies a WordPress site utilizing the ACPT Premium plugin with a public-facing user form enabled.</li>
<li>Attacker interacts with the public form to capture the request structure intended for the <code>submit()</code> function.</li>
<li>Attacker crafts a malicious HTTP POST request targeting the <code>submit()</code> function endpoint.</li>
<li>Attacker injects a target user ID (e.g., ID 1 for the default administrator) into the request parameters.</li>
<li>Attacker includes a new, controlled email address and password within the request body.</li>
<li>The plugin fails to validate the request sender's authorization status.</li>
<li>The plugin executes <code>wp_update_user()</code> using the attacker-supplied parameters.</li>
<li>Attacker gains unauthorized administrative access to the WordPress site using the updated credentials.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated attackers to perform a full site takeover by hijacking administrative accounts. This leads to the potential for data exfiltration, total site defacement, and the deployment of additional backdoors or malware within the WordPress environment.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately audit WordPress instances for public-facing forms generated by the ACPT plugin and disable them until the plugin is patched.</li>
<li>Monitor web server logs for suspicious POST requests targeting common plugin submission endpoints if available in documentation.</li>
<li>Apply the vendor-provided security update for ACPT Premium as soon as it is released.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>wordpress</category><category>plugin-vulnerability</category><category>privilege-escalation</category><category>web-application</category></item></channel></rss>