Security readout for executives and security teams
Plain-English summary
WeKan before 8.19 has an authorization flaw in checklist handling. A logged-in user may be able to alter checklist data across boards by changing board and card identifiers. The main business risk is unauthorized modification of project or operational board content, not data theft or service outage based on the supplied CVSS vector.
Executive priority
Treat as a high-priority integrity issue for any shared WeKan environment. Patch promptly if WeKan supports operational, customer, security, or engineering workflows where unauthorized task manipulation could mislead teams or disrupt process control.
Technical view
The issue is a CWE-639 IDOR in checklist creation and related checklist routes. The vulnerable logic does not verify that a supplied cardId belongs to the supplied boardId, enabling cross-board identifier tampering. CVSS 4.0 scores it 7.1: network reachable, low complexity, low privileges, no user interaction, high vulnerable-system integrity impact.
Likely exposure
Exposure likely affects WeKan deployments running versions prior to 8.19, especially internet-accessible or broadly used internal instances with untrusted or many authenticated users. The provided affected-version metadata is incomplete or inconsistent, so confirm installed version against vendor and advisory data.
Exploitation context
The bundle does not show CISA KEV listing or any cited evidence of active exploitation. The stated attack path requires low privileges and no user interaction, so any authenticated user base increases practical risk. No exploit code or weaponized procedure is needed to understand the exposure.
Researcher notes
The strongest evidence is the description, CVSS vector, CWE-639 mapping, and patch reference. Version data in the bundle lists default unaffected with version 0, which conflicts with the narrative "prior to 8.19" statement. Avoid broader product or exploitation claims without vendor/advisory confirmation.
Mitigation direction
- Upgrade WeKan to version 8.19 or later.
- Review the referenced patch commit for deployed code parity.
- Restrict access to WeKan until upgraded, especially for untrusted users.
- Check vendor guidance for any additional fixed releases or configuration advice.
- Monitor board and checklist changes for unauthorized cross-board activity.
Validation and detection
- Inventory all WeKan instances and record their versions.
- Confirm whether each instance is below 8.19.
- Review access logs for checklist route activity by unexpected users.
- Check application audit trails for checklist changes across unrelated boards.
- Verify the deployed code includes board-card ownership validation.
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-25563 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:N/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:N/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:N/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/5cd875813fdec5a3c40a0358b30a347967c85c14CVE reference, VulnCheck · patch
- https://wekan.fi/CVE reference, VulnCheck · product
- https://www.vulncheck.com/advisories/wekan-checklist-creation-cross-board-idorCVE 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.