<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Malcious Admin Menu Editor Pro plugin backdoors 1,500 WordPress sites]]></title><description><![CDATA[<p dir="auto">A supply chain attack targeting a commercial <strong>WordPress</strong> plugin has left a large number of sites backdoored. Malicious builds of <strong>Admin Menu Editor Pro</strong> were distributed to over <strong>200 customers</strong> after a threat actor compromised the maintainer's website and pushed updates through the plugin's normal distribution channel. Because the plugin is installed on customer sites, those updates reached far beyond the initial victim count, ultimately backdooring more than <strong>1,500 WordPress sites</strong>.</p>
<p dir="auto">The injected code created a hidden user account on affected installations, giving the attacker a persistent foothold for logging in without the site owner's knowledge. This is a classic supply chain pattern: rather than exploiting a vulnerability in the plugin itself, the attacker abused trust in the update mechanism to deliver malicious code directly to customers.</p>
<p dir="auto">Affected parties and key details:</p>
<ul>
<li><strong>Admin Menu Editor Pro</strong> versions distributed via the compromised maintainer website are affected</li>
<li>More than <strong>200 customers</strong> received the malicious updates</li>
<li>Roughly <strong>1,500 WordPress sites</strong> were backdoored as a result</li>
<li>The malicious code creates a hidden administrative user account</li>
</ul>
<p dir="auto">Recommended actions if you run this plugin:</p>
<ul>
<li>Review installed users for accounts you did not create, particularly any with elevated privileges</li>
<li>Remove any unauthorized accounts immediately and rotate all administrator credentials</li>
<li>Check for signs of tampering and treat affected sites as compromised rather than merely outdated</li>
<li>Reinstall the plugin only from a trusted, verified source once the vendor confirms clean builds</li>
</ul>
<p dir="auto">Site owners should also audit logs for unexpected logins and review file integrity where possible, since a hidden account can be used for further persistence or lateral movement.</p>
<p dir="auto">Source: <a href="https://www.bleepingcomputer.com/news/security/malcious-admin-menu-editor-pro-plugin-backdoors-1-500-wordpress-sites" target="_blank" rel="noopener noreferrer nofollow ugc">Unknown</a></p>
<p dir="auto">Have you checked your WordPress installs for unexpected admin accounts since this campaign came to light, and how is your organization handling plugin supply chain risk?</p>
]]></description><link>https://xploitlk.com/topic/350/malcious-admin-menu-editor-pro-plugin-backdoors-1-500-wordpress-sites</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 08:52:06 GMT</lastBuildDate><atom:link href="https://xploitlk.com/topic/350.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 16 Sep 2026 00:30:19 GMT</pubDate><ttl>60</ttl></channel></rss>