CVE-2024-37539 WordPress WP To Do plugin <= 1.3.0 - Cross Site Scripting (XSS) vulnerability
A stored cross-site scripting vulnerability in the WP To Do plugin allows attackers to inject malicious scripts into web pages viewed by other users.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2024-37539?
CVE-2024-37539 is a medium-severity cross-site scripting vulnerability in Delower WP To Do, published on 6 Jul 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Delower WP To Do allows Stored XSS.This issue affects WP To Do: from n/a through 1.3.0.
Weakness: CWE-79
Which versions are affected by CVE-2024-37539?
It affects 1 product.
Products include Delower Wp to Do.
How do I fix CVE-2024-37539?
No fix has been published for CVE-2024-37539 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2024-37539 being exploited?
There is no known exploitation of CVE-2024-37539 in the wild and no public exploit code.
Other vulnerabilities in Delower WP To Do
- 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
- CVE-2024-3945 WP To Do <= 1.3.0 - Cross-Site Request Forgery via wptodo_manage()
Sources
Also known as GHSA-26rv-62pj-28w7.