Security readout for executives and security teams
Plain-English summary
WeKan before 8.19 may let a logged-in user tamper with checklist data across boards by changing object identifiers. The core issue is missing validation that a card belongs to the stated board. This is primarily an integrity risk for task and workflow data, with some availability impact.
Executive priority
Prioritize remediation for shared, customer-facing, or business-critical WeKan instances. The risk is not presented as mass exploitation, but authenticated cross-board tampering can undermine workflow integrity, operational trust, and incident traceability.
Technical view
CVE-2026-25564 is a CWE-639 IDOR in WeKan checklist creation and related checklist routes. Sources say the server failed to verify the supplied cardId belongs to the supplied boardId. CVSS v4.0 is 7.1, with network access, low privileges, no user interaction, high integrity impact, and low availability impact.
Likely exposure
Likely exposure is self-hosted or managed WeKan deployments running versions earlier than 8.19, especially where multiple users share board access. The bundle’s affected-version metadata is sparse, so validate against the CVE record, VulnCheck advisory, and vendor release history.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked KEV. Exploitation is described as authenticated ID tampering over the network, requiring low privileges and no user interaction. Do not assume public exploit availability from this bundle alone.
Researcher notes
Evidence supports an authorization relationship-validation flaw, not a confidentiality breach. The source bundle names checklist creation and related checklist routes, but does not provide complete route details or exploit artifacts. Treat affected-version metadata as incomplete and validate directly against WeKan version 8.19 patch status.
Mitigation direction
- Upgrade WeKan to 8.19 or later after reviewing vendor guidance.
- Verify the referenced patch is present in any maintained fork or custom build.
- Restrict WeKan access to trusted users and networks until upgraded.
- Review account access for users with broad board visibility.
Validation and detection
- Inventory all WeKan deployments and record exact application versions.
- Confirm no production instance runs a version earlier than 8.19.
- Check whether the referenced patch commit exists in deployed builds.
- Review audit logs for unexpected checklist changes across unrelated boards.
- Validate vendor advisories before changing production controls.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-25564 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
7.1HighVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/wekan/wekan/commit/08a6f084eba09487743a7c807fb4a9000fcfa9acCVE reference, VulnCheck · patch
- https://wekan.fi/CVE reference, VulnCheck · product
- https://www.vulncheck.com/advisories/wekan-checklist-deletion-idor-via-missing-relationship-validationCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.