CodeKit · Security record
Is CodeKit safe?
No known vulnerability affects the current version (2.5.3). 4 issues were found in earlier versions and fixed, the latest disclosed on Jul 18, 2023.
Checked 4 days ago against the WPVulnerability database, for version 2.5.3.
How it’s looked after
- Last release
- Oct 12, 2026 (3 weeks ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 7.0.8
- Active installs
- 7K+
4 known vulnerabilities
- 1 high
- 1 medium
- 2 not rated
None affects the current version.
Disclosed each year
- 20223
- 20231
Every known vulnerability in CodeKit
Newest first, with any that affect the current version at the top.
Fixed in 2.3.6 · CVE-2023-33999 · Jul 18, 2023 · Patchstack
Fixed in 2.3 · CVE-2022-4974 · Mar 4, 2022 · Wordfence
Fixed in 2.3 · Feb 28, 2022 · Patchstack
Fixed in 2.3 · Feb 28, 2022 · Patchstack
Questions about CodeKit’s security
Is CodeKit safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep CodeKit updated: most attacks target sites that haven’t updated.
Does CodeKit have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 4 older issues, fixed in earlier versions, so keep CodeKit up to date.
Is CodeKit still maintained?
Yes. Its last release was 3 weeks ago. No support threads were opened in the last two months.
Is CodeKit compatible with the latest WordPress?
It’s tested up to WordPress 7.0.8, one version behind the current 7.1. Authors often update this line a few weeks after a release.
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 freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.