WeKan versions prior to 8.19 contain an authorization weakness in the attachment upload API. The API does not fully validate that provided identifiers (such as boardId, cardId, swimlaneId, and listId) are consistent and refer to a coherent card/board relationship, enabling attempts to upload attachments with mismatched object relationships.
Security readout for executives and security teams
Plain-English summary
This vulnerability affects WeKan attachment uploads before version 8.19. A logged-in user may be able to submit inconsistent board, card, swimlane, or list identifiers and attach content where the relationships should not be allowed. The main business risk is unauthorized modification of project records, not system takeover.
Executive priority
Prioritize remediation for shared, internet-accessible, or customer-facing WeKan systems. This is a high integrity issue, but available sources do not support active exploitation or emergency treatment.
Technical view
The attachment upload API lacks complete authorization validation across related object IDs. CVSS 4.0 rates this 7.1 with network access, low privileges, no user interaction, and high integrity impact. The public description identifies CWE-863 and WeKan versions prior to 8.19.
Likely exposure
Organizations running WeKan before 8.19 are the likely exposure group, especially multi-user instances where authenticated users can upload attachments. The source bundle does not provide enough detail to confirm specific deployment modes or CPE coverage.
Exploitation context
The source bundle says this is not in KEV and provides no cited evidence of active exploitation. The risk is plausible because exploitation requires only a valid low-privilege account and network access to the upload API.
Researcher notes
There is some metadata ambiguity: the affected array is sparse, while the title and description state versions prior to 8.19. Validate exposure against WeKan release data and the linked patch before closing findings.
Mitigation direction
Inventory WeKan deployments and confirm running versions.
Upgrade affected WeKan instances to 8.19 or later.
Review the referenced patch commit against deployed code.
Check WeKan vendor guidance for any additional hardening steps.
Monitor attachment activity for unexpected board or card relationships.
Validation and detection
Confirm each WeKan instance reports version 8.19 or later.
Verify the attachment upload validation patch is present.
Review logs for suspicious attachment uploads by low-privilege users.
Confirm users cannot attach files across unrelated board or card relationships.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
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.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-863 · source CWE mapping
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.