CVE-2026-54833
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnauthenticated Backdoor in Enable CORS <= 2.0.3 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Enable CORS WordPress plugin versions 2.0.3 and below contains an unauthenticated backdoor that allows remote attackers to execute arbitrary code or gain full administrative access to the WordPress site without any authentication credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Enable CORS pluginNavigate to the WordPress installation wp-content/plugins/ directory and check for a folder named 'enable-cors' or similar. If using WordPress admin, go to Plugins > Installed Plugins and look for any plugin with 'CORS' in the name.Affected if The Enable CORS plugin is present in the plugins directory
-
Identify the installed versionOpen the main plugin file (usually enable-cors.php) and locate the version string in the plugin header comment, or check the readme.txt file for the 'Stable tag' entry.Affected if The version listed is 2.0.3 or any version lower (e.g., 2.0.2, 2.0.1, 2.0.0, 1.x)
-
Compare against affected version rangeIf the version cannot be determined, assume the plugin is vulnerable. The vulnerability affects versions 2.0.3 and below per the CVE description.Affected if The plugin version is 2.0.3 or below, or the version cannot be determined but the plugin is present
-
Inspect for unauthorized admin accountsLog into WordPress admin and go to Users > All Users. Review the list for any unfamiliar administrator accounts that were not created by legitimate site administrators.Affected if Unexpected admin accounts exist that were not created by known administrators
A user is affected if the Enable CORS plugin is installed and its version is 2.0.3 or below, or if the version cannot be determined but the plugin is present on the site.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImmediately remove the Enable CORS plugin entirely from the WordPress installation. Conduct a full forensic audit of the site to determine if the backdoor was exploited, and rebuild the environment if compromise is confirmed. Rotate all credentials (admin accounts, database, FTP/SSH, API keys) as a precaution.
Latest version of Enable CORS plugin (version > 2.0.3)
- 1. Verify the current version of the Enable CORS plugin installed on your WordPress site
- 2. Check WordPress plugin repository or patchstack.com for the fixed version release
- 3. Before upgrading, backup your website database and files
- 4. Upgrade the Enable CORS plugin to the latest version available
- 5. Verify the upgrade was successful and the plugin functions correctly
- 6. Review site for any suspicious admin accounts or unauthorized changes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54833 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54833 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data