WP To Do
wp-todo · plugin
Known security vulnerabilities for WP To Do. Find out in seconds which version runs on your site with WP Lens.
7 known vulnerabilities
3 exploitable without logging in · latest Aug 29, 2024
Listed on wordpress.org · latest 2.1.7 · last updated Oct 31, 2025 · 100+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- Medium 5.4
CVE-2024-37539login required≤ 1.3.0
WordPress WP To Do plugin <= 1.3.0 - Cross Site Scripting (XSS) vulnerability
- Medium 5.4
CVE-2024-22292login required≤ 1.2.8
WordPress WP To Do Plugin <= 1.2.8 is vulnerable to Cross Site Scripting (XSS)
- Medium 4.8
CVE-2024-3944admin≤ 1.3.0
WP To Do <= 1.3.0 - Authenticated (Admin+) Stored Cross-Site Scripting via Task Comments
- Medium 4.8
CVE-2024-3946admin≤ 1.3.0
WP To Do <= 1.3.0 - Authenticated (Admin+) Stored Cross-Site Scripting via Settings
- Medium 4.3
CVE-2024-3947unauthenticated · needs a click≤ 1.3.0
WP To Do <= 1.3.0 - Cross-Site Request Forgery via wptodo_settings
- Medium 4.3
CVE-2024-3945unauthenticated · needs a click≤ 1.3.0
WP To Do <= 1.3.0 - Cross-Site Request Forgery via wptodo_manage()
- Medium 4.3
CVE-2024-3943unauthenticated · needs a click≤ 1.3.0
WP To Do <= 1.3.0 - Cross-Site Request Forgery via wptodo_addcomment
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).