{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-3944 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-3944 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-3944 is a medium-severity cross-site scripting vulnerability in delower186 WP To Do, published on 29 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-3944 and fix it if it is affected.\n\nWhat it is: CVE-2024-3944 is a medium-severity cross-site scripting vulnerability in delower186 WP To Do, published on 29 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-3944 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-3944/ (Markdown: https://insights.sbomify.com/CVE-2024-3944/index.md)","id":"CVE-2024-3944","markdown":"https://insights.sbomify.com/CVE-2024-3944/index.md","name":"CVE-2024-3944","record":{"aliases":["GHSA-q57h-cpxr-m8w6"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Administrators can inject scripts via task comments in WP To Do, affecting multi-site or restricted HTML setups.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_to_do","vendor":"delower"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/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 WP To Do plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment in all versions up to, and including, 1.3.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.","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 - Authenticated (Admin+) Stored Cross-Site Scripting via Task Comments","id":"CVE-2024-3944","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"WP To Do \u003c= 1.3.0 - Cross-Site Request Forgery via wptodo_manage()","id":"CVE-2024-3945"},"packages":[],"prev":{"headline":"WP To Do \u003c= 1.3.0 - Cross-Site Request Forgery via wptodo_addcomment","id":"CVE-2024-3943"},"products":["WP To Do"],"published":"2024-08-29","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 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_manage()","id":"CVE-2024-3945","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":"Administrators can inject scripts via task comments in WP To Do, affecting multi-site or restricted HTML setups.","url":"https://insights.sbomify.com/CVE-2024-3944/"}