Unauthenticated content injection via unchecked import
Published Sep 21, 2026 · Updated Sep 21, 2026
Content injection in Trent Jessee To Do List Member 1.4 through 1.6 allows remote attackers to create published posts and terms. Its import routine accepts a caller-supplied data location and imports the fetched data without authorization or nonce validation. No account or user interaction is required; successful requests write attacker-chosen published posts and taxonomy terms to the WordPress site.
Summary
What happened
Content injection in Trent Jessee To Do List Member 1.4 through 1.6 allows remote attackers to create published posts and terms. Its import routine accepts a caller-supplied data location and imports the fetched data without authorization or nonce validation. No account or user interaction is required; successful requests write attacker-chosen published posts and taxonomy terms to the WordPress site.
The record
- CVE
- CVE-2026-86802
- Published
- Sep 21, 2026
- Updated
- Sep 21, 2026
- Vendor
- Trent Jessee
- Product
- To Do List Member
- Classifications
- CWE-345, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 21, 2026CVE publishedPublication date reported by the CVE source.
- Sep 21, 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=1.4 <=1.6
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started