{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-37308 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-37308 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-37308 is a medium-severity cross-site scripting vulnerability in XjSv Cooked, published on 13 Jun 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-37308 and fix it if it is affected.\n\nWhat it is: CVE-2024-37308 is a medium-severity cross-site scripting vulnerability in XjSv Cooked, published on 13 Jun 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-37308 in the wild and no public exploit code.\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-37308/ (Markdown: https://insights.sbomify.com/CVE-2024-37308/index.md)","id":"CVE-2024-37308","markdown":"https://insights.sbomify.com/CVE-2024-37308/index.md","name":"CVE-2024-37308","record":{"aliases":["GHSA-9vfv-c966-jwrv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can inject persistent scripts via recipe settings, allowing arbitrary code execution when pages are viewed.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cooked","vendor":"boxystudio"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"WordPress Cooked Plugin - Authenticated (Contributor+) Persistent Cross-Site Scripting Vulnerability","id":"CVE-2024-37308","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Client initialized Session-Renegotiation DoS","id":"CVE-2024-37309"},"packages":[],"prev":{"headline":"Cilium leaks sensitive information in cilium-bugtool","id":"CVE-2024-37307"},"products":["Cooked"],"published":"2024-06-13","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["XjSv"]},"summary":"Authenticated contributors can inject persistent scripts via recipe settings, allowing arbitrary code execution when pages are viewed.","url":"https://insights.sbomify.com/CVE-2024-37308/"}