dbcve.org
WekanApplication · Wekan Project

CVE-2026-1962

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 has been found in WeKan up to 8.20. The impacted element is an unknown function of the file server/attachmentMigration.js of the component Attachment Migration. The manipulation leads to improper access controls. The attack may be initiated remotely. Upgrading to version 8.21 is sufficient to resolve this issue. The identifier of the patch is 053bf1dfb76ef230db162c64a6ed50ebedf67eee. It is recommended to upgrade the affected component.

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 prior to version 8.21 contains an improper access control vulnerability in the attachment migration functionality (server/attachmentMigration.js). The CVSS 9.8 score indicates this can be exploited remotely with no authentication, allowing unauthorized access to or manipulation of attachments through the migration component.

MitigationUpgrade WeKan to version 8.21 or later to resolve the improper access control vulnerability in the attachment migration component.

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 WeKan installation and version
    Locate the WeKan installation and determine its version number. Common methods include checking the application UI (typically in settings or about page), querying the WeKan API endpoint, or inspecting version files in the installation directory.
    Affected if The installed version is below 8.21 (any version prior to 8.21)
  2. Locate the attachment migration component
    Inspect the WeKan installation directory for the presence of server/attachmentMigration.js. This file contains the vulnerable migration functionality.
    Affected if The file server/attachmentMigration.js exists in the installation
  3. Check if attachment migration is enabled
    Examine WeKan's configuration files, environment variables, or admin settings for any attachment migration feature flags or scheduled tasks that enable the migration component.
    Affected if The attachment migration feature is enabled or configured in the environment
  4. Verify network exposure of migration endpoint
    Determine whether the WeKan server is exposed to network access. The vulnerability is remotely exploitable with no authentication, so an externally accessible WeKan instance is at higher risk.
    Affected if WeKan is reachable over a network without proper authentication guards on the migration functionality

You are affected if WeKan version is below 8.21 and the attachment migration component (server/attachmentMigration.js) is present and accessible in your environment.

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 resolve the improper access control vulnerability in the attachment migration component.

Recommended fix High confidence

Wekan 8.21

  1. Back up your Wekan database and installation before upgrading
  2. Stop the Wekan service
  3. Upgrade Wekan to version 8.21 using your deployment method (e.g., Docker, npm, or source installation)
  4. Verify the upgrade was successful by checking the version
  5. Restart the Wekan service

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

Fix this in Wekan Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1962 — 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-1962 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