WordPress security by component
WP To Do
Plugin description
WP To Do is a WordPress component with 7 published CVE records in this archive. The latest tracked vulnerability was published Aug 29, 2024; the highest CVE/CNA score is 6.5.
Plugin slug:
wp-todoLatest vulnerability
CVE-2024-3944: WP To Do: Cross-site scripting
WP To Do is affected by cross-site scripting. Exploitation requires an authenticated WordPress account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
| Safe version |
|
||
|---|---|---|---|
| Aug 29, 2024 |
CVE-2024-3944
WP To Do: Cross-site scripting
WP To Do is affected by cross-site scripting. Exploitation requires an authenticated WordPress account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE4.4
NVD4.8
|
| Jul 06, 2024 |
CVE-2024-37539
WP To Do: Cross-site scripting
WP To Do is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.5
NVD5.4
|
| May 30, 2024 |
CVE-2024-3947
WP To Do: Cross-site request forgery
WP To Do is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE4.3
NVDPending
|
| May 30, 2024 |
CVE-2024-3946
WP To Do: Cross-site scripting
WP To Do is affected by cross-site scripting. Exploitation requires an authenticated WordPress account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE4.4
NVD4.8
|
| May 30, 2024 |
CVE-2024-3945
WP To Do: Cross-site request forgery
WP To Do is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE4.3
NVDPending
|
| May 30, 2024 |
CVE-2024-3943
WP To Do: Cross-site request forgery
WP To Do is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE4.3
NVD4.3
|
| Jan 31, 2024 |
CVE-2024-22292
WP To Do: Cross-site scripting
WP To Do is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.5
NVD5.4
|