Enable CORS: A security weakness
Enable CORS is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 2.0.3.
- Component
- Enable CORS
- Plugin slug
enable-cors- Affected
- n/a through 2.0.3
- Safe version
2.0.4- Published
- Jun 26, 2026
This CVE was published Jun 26, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update Enable CORS to 2.0.4 or later, or disable and remove it until a fixed version is available.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
Unauthenticated Backdoor in Enable CORS <= 2.0.3 versions.
CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N