dbcve.org
WekanApplication · Wekan Project

CVE-2026-25560

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-07
Fix available
A fix is available. Upgrade to 8.19 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
WeKan versions prior to 8.19 contain an LDAP filter injection vulnerability in LDAP authentication. User-supplied username input is incorporated into LDAP search filters and DN-related values without adequate escaping, allowing an attacker to manipulate LDAP queries during authentication.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

WeKan versions before 8.19 contain an LDAP filter injection vulnerability where user-supplied username input is directly incorporated into LDAP search filters and DN values without proper escaping. An attacker can manipulate the LDAP query by injecting special characters to bypass authentication or enumerate LDAP entries.

MitigationImplement proper LDAP escaping for all user-supplied input before using it in LDAP search filters and DN construction. Use the LDAP library's built-in escaping functions or apply RFC 4515 compliant escaping for special characters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WekanApplication
Affected:< 8.19

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify WeKan installation method
    Determine how WeKan was deployed (e.g., Docker, npm, source) and locate its version information accordingly - check Docker image tags, package.json version field, or the WeKan UI under the 'Version' link in the footer
    Affected if Cannot determine version or version is below 8.19
  2. Confirm installed WeKan version
    Locate and record the exact version number of the WeKan instance
    Affected if Version is lower than 8.19 (e.g., 8.18.x, 8.17.x, earlier releases)
  3. Verify LDAP authentication is in use
    Check WeKan authentication settings to determine if LDAP/Active Directory integration is enabled and configured
    Affected if LDAP authentication is enabled and connected to an LDAP directory
  4. Check for LDAP injection vulnerability
    Review the LDAP configuration for user-supplied input fields (username/filter fields). Attempt to observe how usernames are processed - the vulnerability exists if special LDAP filter characters (*, (, ), \) are not escaped before being inserted into search filters
    Affected if LDAP is enabled and user input is not escaped per RFC 4515 before being used in search filters

You are affected if WeKan version is below 8.19 AND LDAP authentication is configured, because unsanitized usernames in LDAP queries allow injection of special characters to manipulate filter logic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.19 or later
Fixed in 8.19
Vendor patch github.com →
Interim mitigation

Implement proper LDAP escaping for all user-supplied input before using it in LDAP search filters and DN construction. Use the LDAP library's built-in escaping functions or apply RFC 4515 compliant escaping for special characters.

Recommended fix High confidence

Wekan 8.19

  1. 1. Back up your existing Wekan installation and database before upgrading.
  2. 2. Obtain Wekan version 8.19 from the official GitHub releases or package repository.
  3. 3. Upgrade your Wekan installation to version 8.19 using your deployment method (e.g., Docker, npm, or source).
  4. 4. Verify that the upgrade completed successfully by checking the Wekan version in the UI or via API.
  5. 5. Test LDAP authentication functionality to confirm the fix is working properly.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wekan Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25560 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25560 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data