<?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>Amelia — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/amelia/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 07 Apr 2026 07:16:24 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/amelia/feed.xml" rel="self" type="application/rss+xml"/><item><title>Amelia WordPress Plugin IDOR Vulnerability CVE-2026-5465</title><link>https://feed.craftedsignal.io/briefs/2026-04-amelia-idor/</link><pubDate>Tue, 07 Apr 2026 07:16:24 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-amelia-idor/</guid><description>The Amelia WordPress plugin is vulnerable to an insecure direct object reference, allowing authenticated attackers with Provider-level access or higher to escalate privileges and gain persistence by taking over any WordPress account, including Administrator by manipulating the `externalId` field.</description><content:encoded><![CDATA[<p>The Amelia WordPress plugin, specifically the &ldquo;Booking for Appointments and Events Calendar&rdquo;, contains an Insecure Direct Object Reference (IDOR) vulnerability (CVE-2026-5465) in versions up to and including 2.1.3. This flaw resides within the <code>UpdateProviderCommandHandler</code> and stems from insufficient validation when a Provider (Employee) user modifies their profile. The critical issue is the ability to manipulate the <code>externalId</code> field, which directly corresponds to a WordPress user ID. By injecting an arbitrary <code>externalId</code> value during a profile update, an authenticated attacker with Provider-level access or higher can bypass authorization checks. This oversight permits the attacker to execute functions such as <code>wp_set_password()</code> and <code>wp_update_user()</code> on behalf of any other user, including those with Administrator privileges. This vulnerability allows for complete account takeover, representing a significant risk for organizations utilizing the vulnerable plugin.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains authenticated access to a WordPress instance with the Amelia plugin installed, possessing at least Provider (Employee) level privileges.</li>
<li>The attacker navigates to their user profile within the Amelia plugin interface.</li>
<li>The attacker intercepts the HTTP request generated when updating their profile using a tool like Burp Suite or browser developer tools.</li>
<li>The attacker modifies the <code>externalId</code> parameter within the intercepted HTTP request, replacing its original value with the WordPress user ID of the target account they wish to compromise (e.g., the Administrator account, typically user ID 1).</li>
<li>The attacker sends the modified HTTP request to the server.</li>
<li>Due to the IDOR vulnerability, the <code>UpdateProviderCommandHandler</code> fails to validate the manipulated <code>externalId</code> value.</li>
<li>The Amelia plugin&rsquo;s backend utilizes the attacker-controlled <code>externalId</code> to call <code>wp_set_password()</code> and/or <code>wp_update_user()</code> on the target account.</li>
<li>The attacker successfully changes the password or other profile details of the target account, achieving complete account takeover and escalating privileges.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-5465 allows an attacker with minimal privileges (Provider/Employee role) to compromise any other account on the WordPress instance, including Administrator accounts. This grants the attacker full control over the WordPress site, enabling them to install malicious plugins, modify content, exfiltrate sensitive data, or further compromise the underlying server. The number of potential victims is directly proportional to the number of websites utilizing the vulnerable Amelia plugin. Given the plugin&rsquo;s popularity, a successful mass exploitation could impact thousands of websites across various sectors.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately update the Amelia WordPress plugin to the latest version (greater than 2.1.3) to patch CVE-2026-5465.</li>
<li>Monitor web server logs for POST requests to the <code>/wp-admin/admin-ajax.php</code> endpoint with the <code>action</code> parameter set to <code>am_update_provider</code> and a modified <code>externalId</code> parameter in the request body. Implement the Sigma rule <code>Detect Amelia Plugin IDOR Attack</code> to detect such activity.</li>
<li>Implement strong password policies and multi-factor authentication for all WordPress accounts, including those with limited privileges, to mitigate the impact of potential account compromises.</li>
<li>Review and audit existing WordPress user accounts and their assigned roles to identify and remove any unnecessary or excessive privileges.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>wordpress</category><category>amelia</category><category>idor</category><category>privilege-escalation</category></item></channel></rss>