Wekan is open source kanban built with Meteor. Prior to 9.37, Wekan DDP update allow rules in server/permissions/cards.js, server/permissions/lists.js, and server/permissions/swimlanes.js authorize against the stored source boardId and do not validate a new boardId in the update modifier. Any authenticated user with write access to their own board can call /cards/update, /lists/update, or /swimlanes/update to move cards, lists, or swimlanes into a private board they are not a member of. This issue is fixed in version 9.37.
CVE-2026-55234
This high-severity CVE scores 8.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.5
- EG Score
- 8.5(low)
- EPSS
- —
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (3)
Auto-updated Jul 15, 2026Broken access control: any authenticated user can move their Cards/Lists/Swimlanes into a private board they are not a member of (cross-board write via collection allow rule) · Advisory · wekan/wekan · GitHub
https://github.com/wekan/wekan/security/advisories/GHSA-gm7v-pc38-53jrv9.37
Patch available: wekan/wekan v9.37
https://github.com/wekan/wekan/releases/tag/v9.37commit d369a3614a47 (wekan/wekan)
Fix landed in wekan/wekan commit d369a3614a47 — awaiting tagged release
https://github.com/wekan/wekan/commit/d369a3614a4737c29d48a6345a790edf2506ddaeWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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 21:24 UTCEG score recompute
- 2026-07-15 21:23 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-284
- CVE-2015-10057NVD 4.6EG 9.8MEDIUM
- CVE-2010-5305EG 9.8EPSS 92%CRITICAL
- CVE-2015-9209EG 9.8CRITICAL
- CVE-2015-9152EG 9.8CRITICAL
- CVE-2014-10059EG 9.8CRITICAL
- CVE-2014-10053EG 9.8CRITICAL
- CVE-2014-10050EG 9.8CRITICAL
- CVE-2015-0150EG 9.8CRITICAL
- CVE-2014-2048EG 9.8CRITICAL
- CVE-2013-0422EG 9.8 KEVEPSS 100%CRITICAL
Frequently asked(4)
What is CVE-2026-55234?
When was CVE-2026-55234 disclosed?
What is the CVSS score of CVE-2026-55234?
How do I remediate CVE-2026-55234?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-55234
Is Your Infrastructure Affected by CVE-2026-55234?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.