# CVE-2024-39679: WordPress Cooked Plugin - Cross-Site Request Forgery to Recipe Template Reset

> Attackers can trick authenticated users into resetting recipe templates via CSRF, requiring an upgrade to the Cooked WordPress plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-2jh3-9939-c4rc

## What is CVE-2024-39679?

CVE-2024-39679 is a medium-severity vulnerability in XjSv Cooked, published on 17 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-39679?

It affects 1 product.


Products: Boxystudio Cooked.

## How do I fix CVE-2024-39679?

No fix has been published for CVE-2024-39679 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-39679 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39679 exists.

## Other vulnerabilities in XjSv Cooked

- [CVE-2022-3900](https://insights.sbomify.com/CVE-2022-3900/): Cooked Pro < 1.7.5.7 - Unauthenticated PHP Object Injection (critical 9.8)
- [CVE-2023-44477](https://insights.sbomify.com/CVE-2023-44477/): WordPress Cooked Plugin <= 1.7.13 is vulnerable to Cross Site Scripting (XSS) (medium 6.5)
- [CVE-2024-39682](https://insights.sbomify.com/CVE-2024-39682/): WordPress Cooked Plugin - Authenticated (Contributor+) HTML Injection via Recipe Excerpt (medium 6.4)
- [CVE-2021-24233](https://insights.sbomify.com/CVE-2021-24233/): Cooked Pro < 1.7.5.6 - Unauthenticated Reflected Cross Site Scripting (XSS) (medium 6.1)
- [CVE-2024-41816](https://insights.sbomify.com/CVE-2024-41816/): WordPress Cooked Plugin Persistent Cross-Site Scripting via Shortcode (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-39679 and fix it if it is affected.

What it is: CVE-2024-39679 is a medium-severity vulnerability in XjSv Cooked, published on 17 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39679 exists.

Affected product: XjSv Cooked. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-39679/ (Markdown: https://insights.sbomify.com/CVE-2024-39679/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-39679
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-39679
- OSV: https://osv.dev/vulnerability/CVE-2024-39679

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-39679/
Summaries are generated and may contain mistakes; the official description above is the record.