dbcve.org
WekanApplication · Wekan Project

CVE-2026-1963

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-05
Fix available
A fix is available. Upgrade to 8.21 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 mitigates this issue. The patch is identified as c413a7e860bc4d93fe2adcf82516228570bf382d. Upgrading the affected component is advised.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

WeKan kanban application versions up to 8.20 contain improper access controls in the Attachment Storage component (models/attachments.js), allowing remote attackers to access attachments without proper authorization. This is a critical access control bypass vulnerability.

MitigationUpgrade WeKan to version 8.21 or later to apply the patch (c413a7e) that corrects the access control checks in attachment storage. This is a critical-severity vulnerability requiring immediate remediation given remote exploitability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WekanApplication
Affected:< 8.21

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed WeKan version
    Run the command: docker ps (if Docker) or check the package.json in the WeKan installation directory. Alternatively, access the WeKan web UI, click on the user avatar (bottom-left), and look for the version number displayed in the footer or about section.
    Affected if The displayed version is less than 8.21 (for example, 8.20, 8.19, etc.) or if the version cannot be determined and is assumed to be an older release.
  2. Confirm attachment storage is in use
    Check if boards, cards, or user profiles in the WeKan instance contain uploaded files, images, or attachments. Look for the presence of files in the uploads directory (typically /home/wekan/uploads or the configured storage path).
    Affected if The WeKan instance has any attachments stored, meaning the vulnerable attachment storage component is active and accessible.
  3. Inspect models/attachments.js for authorization checks
    Locate the file models/attachments.js in the WeKan source code or installation. Open the file and examine the functions responsible for serving or returning attachments (such as file downloads or API endpoints). Look for authorization logic that verifies user permissions before allowing access.
    Affected if The file contains no authorization checks, or the checks are missing, commented out, or insufficient before allowing attachment retrieval.
  4. Test unauthenticated attachment access
    If you have a WeKan instance, try constructing a direct URL to an attachment (typically /uploads/Attachments/<attachment-id>/<filename>) using an incognito browser window without logging in. Observe whether the file is served without requiring authentication.
    Affected if The attachment file is returned and displayed without any login prompt or authorization challenge, confirming the vulnerability is present.

If the installed WeKan version is below 8.21 and the attachment storage feature is in use, the environment is likely affected by this improper access control vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.21 or later
Fixed in 8.21
Vendor patch github.com →
Interim mitigation

Upgrade WeKan to version 8.21 or later to apply the patch (c413a7e) that corrects the access control checks in attachment storage. This is a critical-severity vulnerability requiring immediate remediation given remote exploitability.

Recommended fix High confidence

8.21

  1. Back up the WeKan database before proceeding with the upgrade
  2. Stop the WeKan service or container
  3. Upgrade WeKan to version 8.21
  4. Restart the WeKan service or container
  5. Verify the upgrade was successful and the service is running

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wekan Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1963 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1963 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data