Administrator-level stored XSS via unescaped settings output
Published May 30, 2024 · Updated Apr 8, 2026
Stored XSS in WP To Do 1.3.0 and earlier allows remote authenticated users with administrator access to inject scripts through settings. The admin-settings path stores insufficiently sanitized values and later renders them without adequate output escaping, causing the saved script to run when a user opens an affected page. Exploitation is limited to multisite installations or sites where unfiltered_html is disabled, and it permits script execution in a visitor's browser.
Summary
What happened
Stored XSS in WP To Do 1.3.0 and earlier allows remote authenticated users with administrator access to inject scripts through settings. The admin-settings path stores insufficiently sanitized values and later renders them without adequate output escaping, causing the saved script to run when a user opens an affected page. Exploitation is limited to multisite installations or sites where unfiltered_html is disabled, and it permits script execution in a visitor's browser.
The record
- CVE
- CVE-2024-3946
- Published
- May 30, 2024
- Updated
- Apr 8, 2026
- Vendor
- Md Delower Hossain
- Product
- WP To Do
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 30, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo