CVE-2024-3947

WP To Do <= 1.3.0 - Cross-Site Request Forgery via wptodo_settings

MEDIUM
4.3
CVSS Score
Published: May 30, 2024 at 04:31 AM UTC
Updated: June 17, 2026 at 07:45 AM UTC
2 products affected across 2 vendorsWp To DoWP To Do

Using WP To Do by delower186?

Get instant alerts when new vulnerabilities affect WP To Do - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.3
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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_settings() function. This makes it possible for unauthenticated attackers to modify the plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Wp To Do· Delowerwordpress-plugin
95%
v ≤ 1.3.0
WP To Do· DELOWER186wordpress-plugin
60%
v ≤ 1.3.0

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.3MEDIUMWordfence
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-352

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card