Skip to main content
VulnerabilityPublished

CVE-2026-54833: Enable CORS (WordPress plugin) · Use of Hard-coded Cryptographic Key

Affects Enable CORS (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.4 High.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Dev KabirEnable CORSAffected
  • ≥ n/a, < 2.0.4
Fixed in–
npmenable-corspkg:npm/enable-corsOther threatsAffected
  • <=2.0.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is available, consider restricting access to the affected service and monitoring for suspicious activity related to Enable CORS. Avoid using affected versions in production environments if possible.

Description

Unauthenticated Backdoor in Enable CORS <= 2.0.3 versions.

References

Community reviews

Loading reviews…