Authenticated cross-board checklist deletion via unchecked identifiers
Published Feb 7, 2026 · Updated Feb 7, 2026
Authorization bypass in WeKan before 8.19 allows remote authenticated users to delete checklists across boards via crafted REST identifiers. The DELETE route in models/checklists.js checks access to the supplied board but removes the supplied checklist without confirming that the card belongs to that board or that the checklist belongs to that card. An authenticated user with access to one board can therefore supply identifiers from another board and delete its checklist, with no broader read access established.
Summary
What happened
Authorization bypass in WeKan before 8.19 allows remote authenticated users to delete checklists across boards via crafted REST identifiers. The DELETE route in models/checklists.js checks access to the supplied board but removes the supplied checklist without confirming that the card belongs to that board or that the checklist belongs to that card. An authenticated user with access to one board can therefore supply identifiers from another board and delete its checklist, with no broader read access established.
The record
- CVE
- CVE-2026-25564
- Published
- Feb 7, 2026
- Updated
- Feb 7, 2026
- Vendor
- WeKan
- Product
- WeKan
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 7, 2026CVE publishedPublication date reported by the CVE source.
- Feb 7, 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 <8.19
What conditions does exploitation require?
What is affected?
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