Is CVE-2026-25560 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-25560 being exploited in the wild.

How severe is CVE-2026-25560?

Critical severity, with a CVSS score of 9.8, published 7 February 2026.

Is there a fix for CVE-2026-25560?

A patch was published on 2026-02-07: Fixed in version 8.19 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-25560 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-25560?

Check whether you run WeKan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-25560: WeKan LDAP filter injection in LDAP authentication

CVE-2026-25560 · Severity: critical · CVSS 9.8 · Published 2026-02-07

WeKan, an open-source Kanban board used for project management, contains a security flaw in its login system. An attacker can provide specially crafted usernames to manipulate the internal database queries used during authentication. This could allow an unauthorized person to bypass security checks, potentially gaining access to sensitive project data or user accounts.

Technologies: WeKan. Vendors: WeKan.

Quick answers

Is CVE-2026-25560 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-25560 being exploited in the wild.
How severe is CVE-2026-25560?: Critical severity, with a CVSS score of 9.8, published 7 February 2026.
Which products and versions are affected?: WeKan < 8.19.
Is there a fix for CVE-2026-25560?: A patch was published on 2026-02-07: Fixed in version 8.19 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-25560 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-25560?: Check whether you run WeKan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An LDAP injection vulnerability exists in WeKan's LDAP authentication module (specifically within packages/wekan-ldap/server/ldap.js). The application fails to properly sanitize or escape user-supplied username input before incorporating it into LDAP search filters and Distinguished Name (DN) related values. A remote, unauthenticated attacker can exploit this by submitting crafted authentication requests to manipulate the resulting LDAP query. This can lead to authentication bypass or unauthorized information disclosure from the LDAP directory. The issue is resolved in version 8.19 by implementing proper escaping for the User_Search_Field.

Affected products

WeKan WeKan < 8.19

Timeline

2026-02-07: disclosed
2026-02-07: patched: Fixed in version 8.19
2026-02-07: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.