Skip to main content
CVE-2026-1896VulnerabilityPublished Updated

CVE-2026-1896: WeKan · Improper Access Controls

Affects WeKanSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium · fixed in 8.21 : update WeKan when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.21
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
WeKanAffected
  • =8.0
  • =8.1
  • =8.2
  • =8.3
  • =8.4
  • =8.5
  • =8.6
  • =8.7
  • =8.8
  • =8.9
  • =8.10
  • =8.11
  • =8.12
  • =8.13
  • =8.14
  • =8.15
  • =8.16
  • =8.17
  • =8.18
  • =8.19
  • =8.20
Fixed in–
GitHubwekan/wekanpkg:github/wekan/wekanOther threatsAffected
  • =8.0
  • =8.1
  • =8.2
  • =8.3
  • =8.4
  • =8.5
  • =8.6
  • =8.7
  • =8.8
  • =8.9
  • =8.10
  • =8.11
  • =8.12
  • =8.13
  • =8.14
  • =8.15
  • =8.16
  • =8.17
  • =8.18
  • =8.19
  • =8.20
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade all WeKan instances to version 8.21 or later, where the vulnerability is patched. 2. Implement strict access control policies limiting user privileges to the minimum necessary, reducing the risk posed by limited privilege attackers. 3. Monitor network traffic and application logs for unusual migration operation requests or anomalies involving boardId parameters. 4. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious manipulation of migration-related API calls. 5. Conduct regular security audits and code reviews focusing on access control enforcement in critical components like migration handlers. 6. Isolate WeKan deployments within secure network segments and restrict administrative interfaces to trusted IP addresses. 7. Educate administrators and users about the importance of timely updates and secure configuration management. 8. Consider implementing multi-factor authentication (MFA) for administrative access to further reduce risk from compromised credentials. These steps go beyond generic advice by focusing on the specific migration operation handler and the nature of the vulnerability.

Description

A vulnerability has been found in WeKan up to 8.20. Affected by this vulnerability is the function ComprehensiveBoardMigration of the file server/migrations/comprehensiveBoardMigration.js of the component Migration Operation Handler. The manipulation of the argument boardId leads to improper access controls. The attack is possible to be carried out remotely. Upgrading to version 8.21 addresses this issue. The identifier of the patch is cc35dafef57ef6e44a514a523f9a8d891e74ad8f. Upgrading the affected component is advised.

References

Community reviews

Loading reviews…