Authenticated public-board creation via unchecked permission
Published Feb 7, 2026 · Updated Feb 7, 2026
Incorrect authorization in WeKan before 8.19 allows remote authenticated users to create public boards despite a private-only policy. The Boards insert rule accepted any logged-in caller without checking allowPrivateOnly or rejecting a document whose permission was public, while the REST route copied the requested permission unchanged. Exploitation requires allowPrivateOnly to be enabled and a valid user account; the result is policy-bypassing public exposure of a newly created board.
Summary
What happened
Incorrect authorization in WeKan before 8.19 allows remote authenticated users to create public boards despite a private-only policy. The Boards insert rule accepted any logged-in caller without checking allowPrivateOnly or rejecting a document whose permission was public, while the REST route copied the requested permission unchanged. Exploitation requires allowPrivateOnly to be enabled and a valid user account; the result is policy-bypassing public exposure of a newly created board.
The record
- CVE
- CVE-2026-25568
- Published
- Feb 7, 2026
- Updated
- Feb 7, 2026
- Vendor
- WeKan
- Product
- WeKan
- Classifications
- CWE-863
- 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