CVE-2024-3945 WP To Do <= 1.3.0 - Cross-Site Request Forgery via wptodo_manage()
Unauthenticated attackers can trick administrators into adding todo items via forged requests due to missing nonce validation in the WP To Do plugin.
- 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
- None listed
What is CVE-2024-3945?
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.
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_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.
Weakness: CWE-352
Which versions are affected by CVE-2024-3945?
It affects 1 product.
Products include Delower Wp to Do.
How do I fix CVE-2024-3945?
No fix has been published for CVE-2024-3945 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-3945 being exploited?
There is no known exploitation of CVE-2024-3945 in the wild and no public exploit code.
Other vulnerabilities in delower186 WP To Do
- CVE-2024-37539 WordPress WP To Do plugin <= 1.3.0 - Cross Site Scripting (XSS) vulnerability
- CVE-2024-22292 WordPress WP To Do Plugin <= 1.2.8 is vulnerable to Cross Site Scripting (XSS)
- CVE-2024-3944 WP To Do <= 1.3.0 - Authenticated (Admin+) Stored Cross-Site Scripting via Task Comments
- CVE-2024-3946 WP To Do <= 1.3.0 - Authenticated (Admin+) Stored Cross-Site Scripting via Settings
- CVE-2024-3943 WP To Do <= 1.3.0 - Cross-Site Request Forgery via wptodo_addcomment