Security readout for executives and security teams
Plain-English summary
WeKan before 8.19 allowed an authenticated user to move cards across boards without properly proving they were allowed to use the destination board, list, or swimlane. The main business risk is unauthorized workflow manipulation and data integrity loss inside project boards.
Executive priority
Treat this as a high-priority integrity issue for teams relying on WeKan for operational workflows, approvals, incident tracking, or customer-facing work management. Patch promptly where untrusted or broad user access exists.
Technical view
This is a CWE-863 authorization flaw in WeKan card move logic. Sources state destination board/list/swimlane authorization was inadequate, and destination objects were not validated as belonging to the destination board. CVSS 4.0 is 7.1 high, driven mainly by network reachability, low complexity, low privileges, and high integrity impact.
Likely exposure
Exposure is most likely in self-hosted or managed WeKan deployments running versions earlier than 8.19, especially where many authenticated users share the instance or external collaborators have accounts.
Exploitation context
The bundle does not cite active exploitation, and KEV status is false. Exploitation requires an authenticated low-privileged user, but no user interaction or special attack conditions are indicated by the CVSS vector.
Researcher notes
The key research focus is destination-side authorization and object ownership validation during card moves. Sources do not establish confidentiality impact beyond low vulnerable-system confidentiality, do not cite active exploitation, and do not identify affected products beyond WeKan.
Mitigation direction
- Upgrade affected WeKan deployments to version 8.19 or later.
- Review the referenced patch and vendor guidance before deployment.
- Restrict WeKan access to trusted authenticated users until patched.
- Review board permissions for external or low-trust collaborators.
- Monitor for unexpected card moves across boards, lists, or swimlanes.
Validation and detection
- Inventory all WeKan instances and confirm their running versions.
- Flag any WeKan version earlier than 8.19 as potentially affected.
- Confirm the authorization patch is present in deployed code.
- Review audit data for unusual cross-board card movement.
- Validate expected card-move permissions in a staging environment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-25566 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
7.1HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/wekan/wekan/commit/198509e7600981400353aec6259247b3c04e043eCVE reference, VulnCheck · patch
- https://wekan.fi/CVE reference, VulnCheck · product
- https://www.vulncheck.com/advisories/wekan-cross-board-card-move-without-destination-authorizationCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.