CVE-2026-52890
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 · uneditedWekan is open source kanban built with Meteor. Prior to 9.31, Wekan allows a logged-in board member to insert an attachment document through the /attachments/insert DDP method with attacker-controlled versions.original.path and versions.original.storage fields. The server/permissions/attachments.js insert rule checks only board write access, and FileStoreStrategyFilesystem.getReadStream() in models/lib/fileStoreStrategy.js streams the stored path without a storage-root containment check, allowing arbitrary file reads and denial of service through special files such as /dev/zero. This issue is fixed in version 9.31.
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 confidenceWekan versions prior to 9.31 contain a path traversal vulnerability in the /attachments/insert DDP method where attacker-controlled versions.original.path and versions.original.storage fields are not validated against a storage-root boundary. The insert rule only verifies board write access without validating the file path, allowing authenticated board members to read arbitrary files from the server filesystem and cause denial of service via special device files like /dev/zero.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Wekan installation and versionCheck the Wekan application version by accessing the API endpoint /api/version, the UI footer, or inspecting the Docker/container logs. On self-hosted installations, check the Wekan bundle or package version file.Affected if The installed version is prior to 9.31 (e.g., 9.30, 9.0, 8.x, 7.x, etc.)
-
Verify the DDP endpoint is accessibleConfirm the Meteor DDP (Distributed Data Protocol) endpoint is reachable on the WebSocket port (default 443 or 3000). The vulnerable method /attachments/insert is part of the Wekan Meteor methods.Affected if The DDP endpoint responds and accepts method calls, indicating the Wekan server is running and accessible.
-
Confirm user has board member accessVerify that at least one user account exists with board member permissions on any board in the system. This is required for the attacker to be authenticated as a board member to exploit the flaw.Affected if Authenticated board member accounts exist in the Wekan instance, providing the necessary privileges to invoke the /attachments/insert method.
-
Check if attachments feature is enabledInspect the Wekan configuration or database to confirm the attachments feature and FileStore are enabled. The vulnerability affects the filesystem storage backend specifically.Affected if Attachments are enabled and the filesystem storage adapter is in use (not using an alternative backend like S3 if available).
You are affected if Wekan version is below 9.31, the DDP endpoint is accessible, and at least one authenticated user has board member permissions enabling access to the vulnerable /attachments/insert method.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Wekan to version 9.31 or later which includes the storage-root containment check in FileStoreStrategyFilesystem.getReadStream(). If immediate upgrade is not possible, restrict board member permissions and monitor for suspicious attachment access patterns.
9.31
- Upgrade Wekan to version 9.31 or later to resolve the path traversal vulnerability in the /attachments/insert DDP method
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-52890 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-52890 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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