Skip to main content
CVE-2026-1898VulnerabilityPublished Updated

CVE-2026-1898: WeKan · Improper Access Controls

Affects WeKanSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 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 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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 5 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-25.

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 WeKan installations to version 8.21 or later immediately to apply the official patch correcting the access control issue in the LDAP User Sync component. 2. Review and restrict network access to WeKan instances, especially limiting exposure of LDAP synchronization endpoints to trusted networks or VPNs. 3. Implement monitoring and alerting on LDAP synchronization activities to detect anomalous or unauthorized sync attempts. 4. Conduct regular audits of user accounts and synchronization logs to identify potential unauthorized changes. 5. If upgrading immediately is not feasible, consider temporarily disabling LDAP synchronization or isolating the WeKan server to reduce exposure. 6. Apply the principle of least privilege on accounts used for LDAP synchronization to minimize potential damage from exploitation. 7. Educate administrators about the vulnerability and ensure they follow secure configuration best practices for WeKan and LDAP integration. 8. Maintain up-to-date backups of WeKan data to enable recovery in case of compromise. These steps go beyond generic advice by focusing on network segmentation, monitoring, and operational controls specific to the LDAP sync process.

Description

A vulnerability was determined in WeKan up to 8.20. This affects an unknown part of the file packages/wekan-ldap/server/syncUser.js of the component LDAP User Sync. This manipulation causes improper access controls. It is possible to initiate the attack remotely. Upgrading to version 8.21 is able to mitigate this issue. Patch name: 146905a459106b5d00b4f09453a6554255e6965a. You should upgrade the affected component.

References

Community reviews

Loading reviews…