Card modification via read-only access check
Published Feb 7, 2026 · Updated Feb 7, 2026
Incorrect authorization in WeKan before 8.19 allows remote authenticated users with read-only board roles to modify card data through the API. Affected card update routes in models/cards.js call checkBoardAccess, which accepts board readers, instead of enforcing checkBoardWriteAccess. A valid account with a read-only board role is required, and successful exploitation permits unauthorized card edits without granting administrative control.
Summary
What happened
Incorrect authorization in WeKan before 8.19 allows remote authenticated users with read-only board roles to modify card data through the API. Affected card update routes in models/cards.js call checkBoardAccess, which accepts board readers, instead of enforcing checkBoardWriteAccess. A valid account with a read-only board role is required, and successful exploitation permits unauthorized card edits without granting administrative control.
The record
- CVE
- CVE-2026-25565
- Published
- Feb 7, 2026
- Updated
- Feb 7, 2026
- Vendor
- WeKan
- Product
- WeKan
- Classifications
- CWE-863, 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.
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