{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39679 exists.","fix":"No fix has been published for CVE-2024-39679 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2024-39679 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-39679 exists.\n\nAffected product: XjSv Cooked. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-39679/ (Markdown: https://insights.sbomify.com/CVE-2024-39679/index.md)","id":"CVE-2024-39679","markdown":"https://insights.sbomify.com/CVE-2024-39679/index.md","name":"CVE-2024-39679","record":{"aliases":["GHSA-2jh3-9939-c4rc"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick authenticated users into resetting recipe templates via CSRF, requiring an upgrade to the Cooked WordPress plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cooked","vendor":"boxystudio"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"WordPress Cooked Plugin - Cross-Site Request Forgery to Recipe Template Reset","id":"CVE-2024-39679","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Cooked Plugin - Cross-Site Request Forgery to Default Recipe Template Save","id":"CVE-2024-39680"},"packages":[],"prev":{"headline":"WordPress Cooked Plugin - Cross-Site Request Forgery to Get Recipe IDs","id":"CVE-2024-39678"},"products":["Cooked"],"published":"2024-07-17","related":[{"cvss_score":9.8,"headline":"Cooked Pro \u003c 1.7.5.7 - Unauthenticated PHP Object Injection","id":"CVE-2022-3900","kev_date_added":null,"published":"2022-12-12"},{"cvss_score":6.5,"headline":"WordPress Cooked Plugin \u003c= 1.7.13 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-44477","kev_date_added":null,"published":"2023-10-02"},{"cvss_score":6.4,"headline":"WordPress Cooked Plugin - Authenticated (Contributor+) HTML Injection via Recipe Excerpt","id":"CVE-2024-39682","kev_date_added":null,"published":"2024-07-17"},{"cvss_score":6.1,"headline":"Cooked Pro \u003c 1.7.5.6 - Unauthenticated Reflected Cross Site Scripting (XSS)","id":"CVE-2021-24233","kev_date_added":null,"published":"2021-04-22"},{"cvss_score":5.4,"headline":"WordPress Cooked Plugin Persistent Cross-Site Scripting via Shortcode","id":"CVE-2024-41816","kev_date_added":null,"published":"2024-08-05"},{"cvss_score":5.4,"headline":"WordPress Cooked Plugin - Cross-Site Request Forgery to Default Recipe Template Save","id":"CVE-2024-39680","kev_date_added":null,"published":"2024-07-17"},{"cvss_score":5.4,"headline":"WordPress Cooked Plugin - Cross-Site Request Forgery to Apply Template to All Recipes","id":"CVE-2024-39681","kev_date_added":null,"published":"2024-07-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["XjSv"]},"summary":"Attackers can trick authenticated users into resetting recipe templates via CSRF, requiring an upgrade to the Cooked WordPress plugin.","url":"https://insights.sbomify.com/CVE-2024-39679/"}