PatchSiren cyber security CVE debrief
CVE-2026-86801 To Do List Member CVE debrief
CVE-2026-86801 debrief based on the supplied source corpus. The To Do List Member WordPress plugin from 1.4 through 1.6 has a file upload endpoint that does not load WordPress and therefore applies no authentication, capability or nonce check of any kind, and validates only the name of an uploaded file rather than its content, allowing unauthenticated users to store active content served from the site's own origin, and to list and delete the files already staged there. Defenders should assess exposure and prioritize remediation.
- Vendor
- To Do List Member
- Product
- To Do List Member WordPress plugin (versions 1.4 through 1.6)
- CVSS
- HIGH 8.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-17
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-09-17
- Advisory updated
- 2026-09-18
Who should care
Defenders responsible for WordPress installations using the To Do List Member plugin should assess exposure and prioritize remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify and remediate this vulnerability in their WordPress installations.
Why it matters
CVE-2026-86801 is a high-severity vulnerability in the To Do List Member WordPress plugin that allows unauthenticated file uploads, enabling attackers to execute malicious content and potentially serve it from the site's origin. Defenders should prioritize verifying and remediating this vulnerability in their WordPress installations.
- Unauthenticated file upload allows active content execution
- Potential for malicious content serving from the site's origin
- Possible unauthorized file listing and deletion
Technical summary
The To Do List Member WordPress plugin from 1.4 through 1.6 has a file upload endpoint that does not load WordPress and therefore applies no authentication, capability or nonce check of any kind, and validates only the name of an uploaded file rather than its content, allowing unauthenticated users to store active content served from the site's own origin, and to list and delete the files already staged there.
Defensive priority
Defenders should prioritize verifying and remediating this vulnerability in their WordPress installations.
Recommended defensive actions
- Verify and remediate vulnerable To Do List Member WordPress plugin installations
- Implement authentication and validation checks for file uploads
- Monitor for suspicious file upload activity
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The To Do List Member WordPress plugin from 1.4 through 1.6 has a file upload endpoint that does not apply authentication, capability, or nonce checks, and only validates the name of an uploaded file. This allows unauthenticated users to store active content served from the site's own origin and list and delete staged files.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-86801 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-86801
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-86801 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-86801
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://wpscan.com/vulnerability/baebde16-141c-4de4-8ecb-173c25bed40d/
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.