HomeWordPress vulnerabilitiesCooked
Cooked vulnerabilities
Cooked has 9 known vulnerabilities in this database. The most recent published record is dated 5 Aug 2024.
- Known vulnerabilities
- 9
- Active installs
- 3,000+
- Latest version
- 1.16.1
- Last updated
- 12 Sep 2026
- Most recent
- 5 Aug 2024
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2024-41816 | Medium 5.4 | Before 1.8.1 | Fixed in 1.8.1 | 5 Aug 2024 |
| Content injection CVE-2024-39682 | Medium 6.4 | Before 1.8.0 | Fixed in 1.8.0 | 18 Jul 2024 |
| Cross-site request forgery (CSRF) CVE-2024-39678 | Medium 4.3 | Before 1.8.0 | Fixed in 1.8.0 | 18 Jul 2024 |
| Cross-site request forgery (CSRF) CVE-2024-39679 | Medium 4.3 | Before 1.8.0 | Fixed in 1.8.0 | 18 Jul 2024 |
| Cross-site request forgery (CSRF) CVE-2024-39680 | Medium 5.4 | Before 1.8.0 | Fixed in 1.8.0 | 18 Jul 2024 |
| Cross-site request forgery (CSRF) CVE-2024-39681 | Medium 5.4 | Before 1.8.0 | Fixed in 1.8.0 | 18 Jul 2024 |
| Cross-site scripting (XSS) CVE-2024-37308 | Medium 5.4 | Before 1.8.0 | Fixed in 1.8.0 | 13 Jun 2024 |
| PHP object injection CVE-2022-3900 | Critical 9.8 | Before 1.7.5.7 | Fixed in 1.7.5.7 | 12 Dec 2022 |
| Cross-site scripting (XSS) CVE-2021-24233 | Medium 6.1 | Before 1.7.5.6 | Fixed in 1.7.5.6 | 22 Apr 2021 |
Read the published descriptions
- CVE-2024-41816, 5 Aug 2024
- Cooked is a recipe plugin for WordPress. The Cooked plugin for WordPress is vulnerable to Persistent Cross-Site Scripting (XSS) via the ‘[cooked-timer]’ shortcode in versions up to, and including, 1.8.0 due to insufficient input sanitization and output escaping. This vulnerability allows authenticated attackers with subscriber-level access and above to inject arbitrary web scripts in pages that will execute whenever a user accesses a compromised page. This issue has been addressed in release version 1.8.1. All users are advised to upgrade. There are no known workarounds for this vulnerability. CVE record
- CVE-2024-39682, 18 Jul 2024
- Cooked is a recipe plugin for WordPress. The Cooked plugin for WordPress is vulnerable to HTML Injection in versions up to, and including, 1.7.15.4 due to insufficient input sanitization and output escaping. This vulnerability allows authenticated attackers with contributor-level access and above to inject arbitrary HTML in pages that will be shown whenever a user accesses a compromised page. This issue has been addressed in release version 1.8.0. Users are advised to upgrade. There are no known workarounds for this vulnerability. CVE record
- CVE-2024-39678, 18 Jul 2024
- Cooked is a recipe plugin for WordPress. The Cooked plugin is vulnerable to Cross-Site Request Forgery (CSRF) in versions up to, and including, 1.7.15.4 due to missing or incorrect nonce validation on the AJAX action handler. This vulnerability could allow an attacker to trick users into performing an action they didn't intend to perform under their current authentication. This issue has been addressed in release version 1.8.0. Users are advised to upgrade. There are no known workarounds for this vulnerability. CVE record
- CVE-2024-39679, 18 Jul 2024
- Cooked is a recipe plugin for WordPress. The Cooked plugin for WordPress is vulnerable to Cross-Site Request Forgery (CSRF) in versions up to, and including, 1.7.15.4 due to missing or incorrect nonce validation on the AJAX action handler. This vulnerability could allow an attacker to trick users into performing an action they didn't intend to perform under their current authentication. This issue has been addressed in release version 1.8.0. Users are advised to upgrade. There are no known workarounds for this vulnerability. CVE record
- CVE-2024-39680, 18 Jul 2024
- Cooked is a recipe plugin for WordPress. The Cooked plugin for WordPress is vulnerable to Cross-Site Request Forgery (CSRF) in versions up to, and including, 1.7.15.4 due to missing or incorrect nonce validation on the AJAX action handler. This vulnerability could allow an attacker to trick users into performing an action they didn't intend to perform under their current authentication. This issue has been addressed in release version 1.8.0. Users are advised to upgrade. There are no known workarounds for this vulnerability. CVE record
- CVE-2024-39681, 18 Jul 2024
- Cooked is a recipe plugin for WordPress. The Cooked plugin for WordPress is vulnerable to Cross-Site Request Forgery (CSRF) in versions up to, and including, 1.7.15.4 due to missing or incorrect nonce validation on the AJAX action handler. This vulnerability could allow an attacker to trick users into performing an action they didn't intend to perform under their current authentication. This issue has been addressed in release version 1.8.0. Users are advised to upgrade. There are no known workarounds for this vulnerability. CVE record
- CVE-2024-37308, 13 Jun 2024
- The Cooked Pro recipe plugin for WordPress is vulnerable to Persistent Cross-Site Scripting (XSS) via the `_recipe_settings[post_title]` parameter in versions up to, and including, 1.7.15.4 due to insufficient input sanitization and output escaping. This vulnerability allows authenticated attackers with contributor-level access and above to inject arbitrary web scripts in pages that will execute whenever a user accesses a compromised page. A patch is available at commit 8cf88f334ccbf11134080bbb655c66f1cfe77026 and will be part of version 1.8.0. CVE record
- CVE-2022-3900, 12 Dec 2022
- The Cooked Pro WordPress plugin before 1.7.5.7 does not properly validate or sanitize the recipe_args parameter before unserializing it in the cooked_loadmore action, allowing an unauthenticated attacker to trigger a PHP Object injection vulnerability. CVE record
- CVE-2021-24233, 22 Apr 2021
- The Cooked Pro WordPress plugin before 1.7.5.6 was affected by unauthenticated reflected Cross-Site Scripting issues, due to improper sanitisation of user input while being output back in pages as an arbitrary attribute. CVE record
What to do if you run Cooked
If you run Cooked, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Cooked vulnerabilities
Free. We email you when a new vulnerability is published for Cooked, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.