Skip to main content
VulnerabilityPublished Updated

CVE-2026-1892: WeKan · Improper Authorization

Affects WeKanSource CVE Database V5

0

Not known to be exploited · CVSS 2.3 Low.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/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 26 Oct 2026.

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

To mitigate CVE-2026-1892, organizations should upgrade all WeKan instances to version 8.21 or later, which includes the official patch (cabfeed9a68e21c469bf206d8655941444b9912c) that corrects the authorization logic in the setBoardOrgs function. Additionally, administrators should audit API access logs for unusual or unauthorized activity related to board or card modifications. Implement network-level restrictions to limit access to the WeKan REST API only to trusted users and systems. Employ strong authentication and role-based access controls within WeKan to minimize the risk of low-privilege accounts being exploited. Regularly review and update permissions assigned to users and API clients to ensure least privilege principles. If upgrading immediately is not feasible, consider temporarily disabling or restricting the affected API endpoints to reduce exposure. Finally, monitor security advisories from the WeKan project and related vulnerability databases for any updates or emerging exploit reports.

Description

A security vulnerability has been detected in WeKan up to 8.20. This affects the function setBoardOrgs of the file models/boards.js of the component REST API. Such manipulation of the argument item.cardId/item.checklistId/card.boardId leads to improper authorization. The attack may be launched remotely. A high complexity level is associated with this attack. The exploitability is reported as difficult. Upgrading to version 8.21 mitigates this issue. The name of the patch is cabfeed9a68e21c469bf206d8655941444b9912c. It is suggested to upgrade the affected component.

References

Community reviews

Loading reviews…