Wekan versions prior to 8.20 allow non-administrative users to access migration functionality due to insufficient permission checks, potentially resulting in unauthorized migration operations.
Security readout for executives and security teams
Plain-English summary
WeKan versions before 8.20 allowed ordinary logged-in users to reach migration functionality that should be restricted to administrators. That could let a non-admin perform unauthorized migration operations, creating integrity and availability risk for boards and application data.
Executive priority
Prioritize remediation for any production WeKan instance with multiple users. The issue can affect data integrity through unauthorized migration actions, but there is no supplied evidence of active exploitation.
Technical view
CVE-2026-25859 is an insufficient authorization issue, mapped to CWE-863, in WeKan migration functionality before 8.20. The CVSS 4.0 score is 7.1, with network access, low complexity, low privileges, no user interaction, high integrity impact, and low availability impact.
Likely exposure
Organizations running WeKan before 8.20 are potentially exposed, especially where non-admin users can authenticate to the instance. The supplied metadata does not identify specific deployment modes, CPEs, or hosted-service exposure.
Exploitation context
The source bundle does not report active exploitation, and KEV is false. CVSS indicates an authenticated low-privilege network attacker could trigger the vulnerable authorization path without user interaction. No exploit details are provided here.
Researcher notes
Version evidence is partly inconsistent: the title and description state WeKan before 8.20, while the affected metadata lists version "0" with defaultStatus "unaffected." Use the <8.20 statement from the CVE description/advisory and confirm against vendor release data.
Mitigation direction
Upgrade WeKan to version 8.20 or later.
Apply the referenced vendor patch if direct version upgrade is not immediately possible.
Restrict migration functionality to administrators only.
Review vendor guidance for any additional hardening or backport instructions.
Limit non-admin account access until affected instances are remediated.
Validation and detection
Inventory all WeKan instances and record running versions.
Confirm any version before 8.20 is treated as affected.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-863 · source CWE mapping
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.