# CVE-2024-3943: WP To Do <= 1.3.0 - Cross-Site Request Forgery via wptodo_addcomment

> Unauthenticated attackers can trick administrators into adding comments to to-do items via forged requests in the WP To Do 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:** 30 May 2024
- **Updated:** 8 Apr 2026

## What is CVE-2024-3943?

CVE-2024-3943 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.

### Official 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_addcomment function. This makes it possible for unauthenticated attackers to add comments to to do items via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

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

It affects 1 product.


Products: Delower Wp to Do.

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

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

## Is CVE-2024-3943 being exploited?

There is no known exploitation of CVE-2024-3943 in the wild and no public exploit code.

## Other vulnerabilities in delower186 WP To Do

- [CVE-2024-37539](https://insights.sbomify.com/CVE-2024-37539/): WordPress WP To Do plugin <= 1.3.0 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2024-22292](https://insights.sbomify.com/CVE-2024-22292/): WordPress WP To Do Plugin <= 1.2.8 is vulnerable to Cross Site Scripting (XSS) (medium 6.5)
- [CVE-2024-3944](https://insights.sbomify.com/CVE-2024-3944/): WP To Do <= 1.3.0 - Authenticated (Admin+) Stored Cross-Site Scripting via Task Comments (medium 4.4)
- [CVE-2024-3946](https://insights.sbomify.com/CVE-2024-3946/): WP To Do <= 1.3.0 - Authenticated (Admin+) Stored Cross-Site Scripting via Settings (medium 4.4)
- [CVE-2024-3945](https://insights.sbomify.com/CVE-2024-3945/): WP To Do <= 1.3.0 - Cross-Site Request Forgery via wptodo_manage() (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3943 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.
Exploitation: There is no known exploitation of CVE-2024-3943 in the wild and no public exploit code.

Affected product: delower186 WP To Do. 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-3943/ (Markdown: https://insights.sbomify.com/CVE-2024-3943/index.md)
```

## Sources

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

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