Cyber Resilience

CVE-2026-25564

HighPublic PoC

Published: 07 February 2026

Published
07 February 2026
Modified
10 February 2026
KEV Added
Patch
CVSS Score v4 7.1 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0001 2.8th percentile
Risk Priority 14 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2026-25564 is a high-severity Authorization Bypass Through User-Controlled Key (CWE-639) vulnerability in Wekan Project Wekan. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 2.8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified are NIST 800-53 AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement).

Deeper analysis

CVE-2026-25564 is an insecure direct object reference (IDOR) vulnerability, classified under CWE-639, affecting WeKan versions prior to 8.19. The flaw exists in checklist creation and related checklist routes, where the implementation fails to verify that the supplied cardId belongs to the supplied boardId. This allows attackers to manipulate identifiers for cross-board tampering. The vulnerability received a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) and was published on 2026-02-07.

Unauthenticated attackers (PR:N) can exploit this over the network (AV:N) with low complexity (AC:L) and no user interaction (UI:N). By supplying a cardId from a different boardId, they can perform unauthorized actions such as checklist creation or deletion on cards outside their authorized scope, leading to high integrity impact (I:H) without affecting confidentiality or availability.

Mitigation involves updating to WeKan version 8.19 or later, as detailed in the fixing commit at https://github.com/wekan/wekan/commit/08a6f084eba09487743a7c807fb4a9000fcfa9ac, which adds the necessary relationship validation. Additional details are available in the VulnCheck advisory at https://www.vulncheck.com/advisories/wekan-checklist-deletion-idor-via-missing-relationship-validation and on the WeKan site at https://wekan.fi/.

EU & UK References

Vulnerability details

WeKan versions prior to 8.19 contain an insecure direct object reference (IDOR) in checklist creation and related checklist routes. The implementation does not verify that the supplied cardId belongs to the supplied boardId, allowing cross-board ID tampering by manipulating identifiers.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1565.001 Stored Data Manipulation Impact
Adversaries may insert, delete, or manipulate data at rest in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
Why these techniques?

IDOR in public-facing WeKan web app enables unauthenticated network exploitation (T1190) and direct unauthorized stored data tampering via checklist create/delete (T1565.001).

Confidence: HIGH · MITRE ATT&CK Enterprise v18.1

CVEs Like This One

CVE-2026-25563Same product: Wekan Project Wekan
CVE-2026-25561Same product: Wekan Project Wekan
CVE-2026-1963Same product: Wekan Project Wekan
CVE-2026-1962Same product: Wekan Project Wekan
CVE-2026-30845Same product: Wekan Project Wekan
CVE-2026-25859Same product: Wekan Project Wekan
CVE-2026-25560Same product: Wekan Project Wekan
CVE-2026-30846Same product: Wekan Project Wekan
CVE-2026-30844Same product: Wekan Project Wekan
CVE-2026-2206Same product: Wekan Project Wekan

Affected Assets

wekan project
wekan
≤ 8.19

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces authorization checks on supplied cardId and boardId so that checklist operations cannot be performed on objects outside the caller's authorized scope.

prevent

Enforces information-flow rules between boards and cards, blocking the cross-board identifier tampering that the missing relationship validation permits.

prevent

Requires validation of input parameters (cardId vs. boardId) to reject inconsistent or unauthorized object references before any checklist action is executed.

References