Enable CORS · Security record

Is Enable CORS safe?

No known vulnerability affects the current version (3.0.0). 1 issue was found in earlier versions and fixed, the latest disclosed on Jun 18, 2026.

Checked 5 days ago against the WPVulnerability database, for version 3.0.0.

How it’s looked after

Last release: Oct 25, 2026 (2 weeks ago)
Releases in the last year: 2
Tested up to: WordPress 7.1.4
Support resolved: 1 of 1 threads in two months
Active installs: 5K+

1 known vulnerability

1 high

None affects the current version.

Every known vulnerability in Enable CORS

Newest first, with any that affect the current version at the top.

high
Backdoor
Fixed in 2.0.4 · CVE-2026-54833 · Jun 18, 2026 · Wordfence

Questions about Enable CORS’s security

Is Enable CORS safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Enable CORS updated: most attacks target sites that haven’t updated.

Does Enable CORS have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Enable CORS up to date.

Is Enable CORS still maintained?

Yes. Its last release was 2 weeks ago. Its authors resolved 1 of the 1 support threads opened in the last two months.

Is Enable CORS compatible with the latest WordPress?

Yes. It’s tested up to WordPress 7.1.4, the current version.

Hear about the next one first

Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.

Start free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.