# CVE-2026-86801: To Do List Member 1.4 - 1.6 - Unauthenticated Stored XSS, File Listing and Deletion via Unprotected Upload Handler

> Unauthenticated attackers can inject malicious scripts and manage files via an unprotected upload handler in the To Do List Member plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-347f-487h-46gq

## What is CVE-2026-86801?

CVE-2026-86801 is a high-severity cross-site scripting vulnerability in Unknown To Do List Member, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The To Do List Member WordPress plugin from 1.4 through 1.6 ships 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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-86801?


## How do I fix CVE-2026-86801?

No fix has been published for CVE-2026-86801 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-86801 being exploited?

There is no known exploitation of CVE-2026-86801 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86801 and fix it if it is affected.

What it is: CVE-2026-86801 is a high-severity cross-site scripting vulnerability in Unknown To Do List Member, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-86801 in the wild and no public exploit code.

Affected product: Unknown To Do List Member. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-86801/ (Markdown: https://insights.sbomify.com/CVE-2026-86801/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86801
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86801
- OSV: https://osv.dev/vulnerability/CVE-2026-86801

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-86801/
Summaries are generated and may contain mistakes; the official description above is the record.