{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-3945 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-3945 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-3945 is a medium-severity vulnerability in delower186 WP To Do, published on 30 May 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-3945 and fix it if it is affected.\n\nWhat it is: CVE-2024-3945 is a medium-severity vulnerability in delower186 WP To Do, published on 30 May 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: There is no known exploitation of CVE-2024-3945 in the wild and no public exploit code.\n\nAffected product: delower186 WP To Do. 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-3945/ (Markdown: https://insights.sbomify.com/CVE-2024-3945/index.md)","id":"CVE-2024-3945","markdown":"https://insights.sbomify.com/CVE-2024-3945/index.md","name":"CVE-2024-3945","record":{"aliases":[],"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":"Unauthenticated attackers can trick administrators into adding todo items via forged requests due to missing nonce validation in the WP To Do plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_to_do","vendor":"delower"}],"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":"The WP To Do plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.3.0. This is due to missing or incorrect nonce validation on the wptodo_manage() function. This makes it possible for unauthenticated attackers to add new todo items via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"WP To Do \u003c= 1.3.0 - Cross-Site Request Forgery via wptodo_manage()","id":"CVE-2024-3945","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"WP To Do \u003c= 1.3.0 - Authenticated (Admin+) Stored Cross-Site Scripting via Settings","id":"CVE-2024-3946"},"packages":[],"prev":{"headline":"WP To Do \u003c= 1.3.0 - Authenticated (Admin+) Stored Cross-Site Scripting via Task Comments","id":"CVE-2024-3944"},"products":["WP To Do"],"published":"2024-05-30","related":[{"cvss_score":6.5,"headline":"WordPress WP To Do plugin \u003c= 1.3.0 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-37539","kev_date_added":null,"published":"2024-07-06"},{"cvss_score":6.5,"headline":"WordPress WP To Do Plugin \u003c= 1.2.8 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2024-22292","kev_date_added":null,"published":"2024-01-31"},{"cvss_score":4.4,"headline":"WP To Do \u003c= 1.3.0 - Authenticated (Admin+) Stored Cross-Site Scripting via Task Comments","id":"CVE-2024-3944","kev_date_added":null,"published":"2024-08-29"},{"cvss_score":4.4,"headline":"WP To Do \u003c= 1.3.0 - Authenticated (Admin+) Stored Cross-Site Scripting via Settings","id":"CVE-2024-3946","kev_date_added":null,"published":"2024-05-30"},{"cvss_score":4.3,"headline":"WP To Do \u003c= 1.3.0 - Cross-Site Request Forgery via wptodo_addcomment","id":"CVE-2024-3943","kev_date_added":null,"published":"2024-05-30"},{"cvss_score":4.3,"headline":"WP To Do \u003c= 1.3.0 - Cross-Site Request Forgery via wptodo_settings","id":"CVE-2024-3947","kev_date_added":null,"published":"2024-05-30"}],"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":"2026-04-08","vendors":["delower186"]},"summary":"Unauthenticated attackers can trick administrators into adding todo items via forged requests due to missing nonce validation in the WP To Do plugin.","url":"https://insights.sbomify.com/CVE-2024-3945/"}