Security Resilience

CVE-2026-1963

Wekan Project Wekan ≤ 8.21

Published
05 February 2026
Modified
06 March 2026
Patch / advisory
CVSS Score v4 5.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/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.0036 29th percentile
Risk Priority 32 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-1963 is a medium-severity Incorrect Privilege Assignment (CWE-266) vulnerability in Wekan Project Wekan. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Temporary Elevated Cloud Access (T1548.005); ranked at the 29th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-1963 is a vulnerability in WeKan open-source kanban board software versions up to 8.20, specifically affecting an unknown function within the file models/attachments.js of the Attachment Storage component. It stems from improper access controls (mapped to CWE-266 and CWE-284), allowing unauthorized manipulation of attachments. The issue carries a CVSS v3.1 base score of 6.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L), indicating medium severity with network accessibility and low attack complexity.

An authenticated attacker with low privileges can exploit this vulnerability remotely without user interaction. Successful exploitation enables limited impacts, including low-level disclosure of confidential information, modification of data, and denial of service on attachments, potentially compromising board data integrity in multi-user environments.

Mitigation is available via upgrade to WeKan version 8.21, which includes the fixing commit c413a7e860bc4d93fe2adcf82516228570bf382d. Security practitioners should prioritize updating the affected Attachment Storage component, with details in the WeKan GitHub repository, release notes, and related advisories.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A vulnerability was found in WeKan up to 8.20. This affects an unknown function of the file models/attachments.js of the component Attachment Storage. The manipulation results in improper access controls. The attack may be launched remotely. Upgrading to version 8.21…

more

mitigates this issue. The patch is identified as c413a7e860bc4d93fe2adcf82516228570bf382d. Upgrading the affected component is advised.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1548.005 Temporary Elevated Cloud Access Privilege Escalation
Adversaries may abuse permission configurations that allow them to gain temporarily elevated access to cloud resources.
T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
T1543.005 Container Service Persistence
Adversaries may create or modify container or container cluster management tools that run as daemons, agents, or services on individual hosts.
T1609 Container Administration Command Execution
Adversaries may abuse a container administration service to execute commands within a container.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-1898Same product: Wekan Project Wekan
CVE-2026-1962Same product: Wekan Project Wekan
CVE-2026-1964Same product: Wekan Project Wekan
CVE-2026-1895Same product: Wekan Project Wekan
CVE-2026-2206Same product: Wekan Project Wekan
CVE-2026-1896Same product: Wekan Project Wekan
CVE-2025-65780Same product: Wekan Project Wekan
CVE-2025-65779Same product: Wekan Project Wekan
CVE-2026-2207Same product: Wekan Project Wekan
CVE-2026-2205Same product: Wekan Project Wekan

Affected Assets

wekan project
wekan
≤ 8.21

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 8 hardening rules · 6 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

Directly enforces approved authorizations for logical access, stopping unauthorized actors from reaching resources.

Enforces flow-control policies that restrict information movement between subjects and objects.

Documents duties and assigns access so that no single account can bypass intended restrictions.

Least privilege directly requires that only the minimal necessary privileges are assigned to each actor.

Account management defines and authorizes the exact privileges granted to each account or role.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 full match
blocks

Directly enforces least-privilege policy definition, management, and review that prevents incorrect privilege assignments.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.5.15 directly requires determining access needs, defining/enforcing topic-specific access control policy and rules (including need-to-know, privilege restrictions, segregation, formal authorization, role-based mapping, and consistency with classification), which stops most incorrect privilege assignments from being exploitable; the bounded remainder is incorrect assignments that arise from flawed implementation of those rules rather than from their absence.

blocks

A.5.16's identity lifecycle (unique binding, timely disable/remove, no duplicates, oversight of shared/non-human) directly stops most improper access by ensuring the actor in an access decision is correctly identified and authorized; the bounded remainder is non-identity mechanisms in CWE-284 such as path traversal or CSRF that do not turn on actor identity at all.

blocks

A.5.18's provisioning, review, revocation and SoD rules (esp. a,b,c,f,i,j) directly stop most incorrect privilege assignments from being granted or persisting, with a bounded remainder in flawed implementation of the authorization step itself (see 5.9/5.15 dependency)

blocks

A.6.7's policy, rules, mechanisms, authentication requirements, remote access controls, network restrictions, and device measures (e.g. screen locks, firewalls, malware protection) directly stop unauthorized actors from exploiting improper access control in remote settings; remainder is non-remote or physical-only slices of CWE-284 (as in AC-3's own mostly precedent).

blocks

A.8.1 mandates access controls, storage encryption, software restrictions, malware protection, remote lock/wipe, physical/logical device protections, and policy-driven enforcement that stop unauthorized actors from exploiting improper access control on endpoints; remainder is non-endpoint or non-device slices of CWE-284 (e.g. server-side authorization logic).

blocks

A.8.2 directly controls the identification, allocation, review, expiry, and temporary nature of privileged rights per policy, which stops most incorrect assignments from creating an exploitable sphere of control; the bounded remainder is incorrect privilege semantics inside code that the authorization process never sees.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248551 A sticky bit must be set on all OL 8 public directories to prevent unauthorized and unintended information transferred via shared system resources. blocks CWE-266
Oracle Linux 9 (1 rule)
  • V-271779 OL 9 must be configured so that a sticky bit must be set on all public directories. blocks CWE-266
RHEL 8 (1 rule)
  • V-230243 A sticky bit must be set on all RHEL 8 public directories to prevent unauthorized and unintended information transferred via shared system resources. blocks CWE-266
RHEL 9 (1 rule)
  • V-257929 A sticky bit must be set on all RHEL 9 public directories. blocks CWE-266
Ubuntu 22.04 (2 rules)
  • V-260513 Ubuntu 22.04 LTS must set a sticky bit on all public directories to prevent unauthorized and unintended information transferred via shared system resources. blocks CWE-266
  • V-260559 Ubuntu 22.04 LTS must ensure only users who need access to security functions are part of sudo group. blocks CWE-266
Ubuntu 24.04 (2 rules)
  • V-270748 Ubuntu 24.04 LTS must ensure only users who need access to security functions are part of sudo group. blocks CWE-266
  • V-270750 Ubuntu 24.04 LTS must set a sticky bit on all public directories to prevent unauthorized and unintended information transferred via shared system resources. blocks CWE-266

References