Wekan is open source kanban built with Meteor. Prior to 9.64, Wekan has a cross-board authorization bypass in the direct Meteor collection allow rules for Checklists and ChecklistItems because updates are authorized only against the current source doc.cardId and do not inspect the destination cardId or boardId in the update modifier, allowing a low-privileged authenticated user with write access to one board and knowledge of a target private card id to create checklist data on an accessible card and move it into a private board where they are not a member. This issue is fixed in version 9.64.
CVE-2026-59154
This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(medium)
- EPSS
- 11.0%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
Advisory Details (3)
Auto-updated Jul 10, 2026Checklist direct DDP updates can write checklist data into private boards · Advisory · wekan/wekan · GitHub
https://github.com/wekan/wekan/security/advisories/GHSA-gv8h-5p3p-6hx7v9.64
Patch available: wekan/wekan v9.64
https://github.com/wekan/wekan/releases/tag/v9.64commit b1ca76007b9a (wekan/wekan)
Fix landed in wekan/wekan commit b1ca76007b9a — awaiting tagged release
https://github.com/wekan/wekan/commit/b1ca76007b9a295fd029dfefc1a2d1d6f1920835Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 10:29 UTCEG score recompute
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 12:01 UTCEG score recompute
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 13:32 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 15:03 UTCEG score recompute
- 2026-07-10 16:33 UTCEG score recompute
- 2026-07-10 16:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-59154?
When was CVE-2026-59154 disclosed?
Is CVE-2026-59154 actively exploited?
What is the CVSS score of CVE-2026-59154?
How do I remediate CVE-2026-59154?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59154
Is Your Infrastructure Affected by CVE-2026-59154?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.