Skip to main content
VulnerabilityPublished Updated

CVE-2025-65780: wekan · Improper Access Control

Affects wekanSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 18.16 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 18.16
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Dec 2025

  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

Upgrade wekan/wekan to 18.16.

Affected software

ProductAffectedFixed in
GitHubwekan/wekanpkg:github/wekan/wekanOther threatsAffected
  • <18.16
Fixed in
  • 18.16

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

AI-suggested

To mitigate this vulnerability, European organizations should immediately upgrade Wekan installations to version 18.16 or later, where the authorization checks have been properly implemented. Until patching is complete, restrict access to Wekan to trusted users only and review user privileges to ensure minimal necessary access. Implement network-level controls such as VPNs or IP whitelisting to limit exposure. Conduct thorough audits of user accounts and organizational memberships to detect any unauthorized changes. Employ monitoring and alerting for unusual user document modifications or privilege escalations. Additionally, enforce strong authentication mechanisms, such as multi-factor authentication (MFA), to reduce the risk of compromised credentials. Regularly review and update access control policies to ensure they align with the principle of least privilege. Finally, educate users about the importance of reporting suspicious activity promptly.

Description

An issue was discovered in Wekan The Open Source kanban board system up to version 18.15, fixed in 18.16. Authenticated users can update their entire user document (beyond profile fields), including orgs/teams and loginDisabled, due to missing server-side authorization checks; this enables privilege escalation and unauthorized access to other teams/orgs.

References

Community reviews

Loading reviews…