Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

Cooked · Security record

Is Cooked safe?

No known vulnerability affects the current version (1.17.0). 17 issues were found in earlier versions and fixed, the latest disclosed on Sep 16, 2026.

Checked 2 days ago against the WPVulnerability database, for version 1.17.0.

How it’s looked after

Last release
Nov 1, 2026 (1 week ago)
Releases in the last year
10
Tested up to
WordPress 7.2
Support resolved
1 of 1 threads in two months
Active installs
3K+

17 known vulnerabilities

  • 5 high
  • 7 medium
  • 5 not rated

None affects the current version.

Disclosed each year

  • 20212
  • 20232
  • 20248
  • 20253
  • 20261

Every known vulnerability in Cooked

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

Questions about Cooked’s security

Is Cooked safe to use?

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

Does Cooked have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 17 older issues, fixed in earlier versions, so keep Cooked up to date.

Is Cooked still maintained?

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

Is Cooked compatible with the latest WordPress?

Yes. It’s tested up to WordPress 7.2, ahead of the current 7.1.

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.