Strategic Overview
- Status
- Patched in 2.0.4
- Affected Plugin
- Enable CORS
- Affected Version
<= 2.0.3- CVSS
- 9.8Critical
- Weakness type
- CWE-506 · Embedded Malicious Code
- CVE
CVE-2026-54833
At a glance
CVE-2026-54833 is a critical-severity Embedded Malicious Code vulnerability in the Enable CORS WordPress plugin, affecting versions <= 2.0.3. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.0.4; sites on affected versions should update now. Disclosed June 2026, reported by Ananda Dhakal.
Vulnerability Overview
The Enable CORS plugin contained a backdoor in all versions up to, and including, 2.0.3. This makes it possible for unauthenticated attackers to gain privileged access to a site.
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 Enable CORS <= 2.0.3 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. For Enable CORS the fix is 2.0.4: builds <= 2.0.3 are affected, anything from 2.0.4 onward is not.
Remediation
Update to version 2.0.4, or a newer patched version
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. None of that substitutes for the fix: Enable CORS 2.0.4 closes this, and updating the plugin is the step that ends it.
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C