Admin Menu Editor Pro 2.35 - 2.36 - Backdoored Software
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Admin Menu Editor Pro
- Affected Version
2.35 – 2.36- CVSS
- 9.8Critical
- Weakness type
- CWE-506 · Embedded Malicious Code
- CVE
CVE pending
At a glance
This record tracks a critical-severity Embedded Malicious Code vulnerability in the Admin Menu Editor Pro WordPress plugin, affecting versions 2.35 – 2.36. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed September 2026.
Vulnerability Overview
The Admin Menu Editor Pro plugin for WordPress contains a backdoor in versions 2.35 to 2.36. This is due to their infrastructure getting compromised. This makes it possible for unauthenticated attackers to gain backdoored access to sites running the software.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-506: Embedded Malicious Code
Reaching this weakness in Admin Menu Editor Pro 2.35 – 2.36 takes a caller who can reach the endpoint. Embedded malicious code means functionality was deliberately placed in the software to act against the site owner's interest, rather than being an accidental defect.
Removing the software is not enough on its own — anything it created or modified while active has to be audited too. No fixed build of this plugin is recorded for Admin Menu Editor Pro yet, so installs running 2.35 – 2.36 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C