CVE-2026-54833 WordPress Enable CORS plugin <= 2.0.3 - Backdoor vulnerability
High 7.4
Published
Updated
Check this codebase for CVE-2026-54833 and fix it if it is affected.
What it is: CVE-2026-54833 is a high-severity vulnerability in Dev Kabir Enable CORS, published on 26 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54833 in the wild and no public exploit code.
Affected product: Dev Kabir Enable CORS. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-54833/ (Markdown: https://insights.sbomify.com/CVE-2026-54833/index.md)
An unauthenticated backdoor in the Enable CORS WordPress plugin allows attackers to execute code and escalate privileges.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-54833?
CVE-2026-54833 is a high-severity vulnerability in Dev Kabir Enable CORS, published on 26 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Unauthenticated Backdoor in Enable CORS <= 2.0.3 versions.
Weakness: CWE-321
Which versions are affected by CVE-2026-54833?
How do I fix CVE-2026-54833?
No fix has been published for CVE-2026-54833 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-54833 being exploited?
There is no known exploitation of CVE-2026-54833 in the wild and no public exploit code.
Sources
Also known as GHSA-j6v4-3f83-jr3w.