Wekan Project Wekan

WeKan < 8.19 LDAP Authentication Filter Injection

WeKan Attachment Storage attachments.js MoveStorageBleed access control

WeKan Attachment Migration attachmentMigration.js AttachmentMigrationBleed access control

Wekan Vulnerable to SSRF through Lack of Validation or Filtering in Attachment URL Loading

Wekan Credential Leak via notificationUsers Publication Exposes Password Hashes and Session Tokens

Wekan has Cross-Board IDOR in Custom Fields Update Endpoints

WeKan < 8.20 Migration Functionality Insufficient Permission Checks

An issue was discovered in Wekan The Open Source kanban board system up to version 18.15, fixed in 18.16. Authenticated users can update their entire user document (beyond profile fields), including orgs/teams and loginDisabled, due to missing server-side authorization checks; this enables privilege escalation and unauthorized access to other teams/orgs.

WeKan Administrative Repair fixDuplicateLists.js FixDuplicateBleed access control

Wekan Exposes All Global Webhook Integrations through globalwebhooks Publication

Wekan Exposes Sensitive Data through Lack of Field Filtering During Board Publication

An issue was discovered in Wekan The Open Source kanban board system up to version 18.15, fixed in 18.16. Attachment upload API treats the Authorization bearer value as a userId and enters a non-terminating body-handling branch for any non-empty bearer token, enabling trivial application-layer DoS and latent identity-spoofing.

packages/wekan-ldap/server/ldap.js in Wekan before 4.87 can process connections even though they are not authorized by the Certification Authority trust store,

An issue was discovered in Wekan The Open Source kanban board system up to version 18.15, fixed in 18.16. Uploaded attachments can be served with attacker-controlled Content-Type (text/html), allowing execution of attacker-supplied HTML/JS in the application's origin and enabling session/token theft and CSRF actions.

WeKan < 8.19 Attachment Upload Object Relationship Validation Bypass

WeKan < 8.19 Checklist Creation Cross-Board IDOR

WeKan < 8.19 Checklist Deletion IDOR via Missing Relationship Validation

An issue was discovered in Wekan The Open Source kanban board system up to version 18.15, fixed in 18.16. Unauthenticated attackers can update a board's "sort" value (Boards.allow returns true without verifying userId), allowing arbitrary reordering of boards.

WeKan < 8.19 Read-only Board Roles Can Update Cards

WeKan < 8.19 allowPrivateOnly Setting Enforcement Bypass

WeKan < 8.19 Cross-board Card Move Without Destination Authorization

WeKan Activity Publication activities.js LinkedBoardActivitiesBleed information disclosure

WeKan Migration Operation comprehensiveBoardMigration.js ComprehensiveBoardMigration MigrationBleed access control

WeKan Attachment Storage lists.js applyWipLimit ListWIPBleed access control

WeKan LDAP User Sync syncUser.js SyncLDAPBleed access control

An issue was discovered in Wekan The Open Source kanban board system up to version 18.15, fixed in 18.16. Authorization flaw in card update handling allows board members (and potentially other authenticated users) to add/remove arbitrary user IDs in vote.positive / vote.negative arrays, enabling vote forgery and unauthorized voting.

WeKan Rules rules.js RulesBleed authorization

WeKan REST API checklistItems.js Checklist REST Bleed improper authorization

WeKan Custom Translation translationBody.js setCreateTranslation improper authorization

A stored cross-site scripting (Stored XSS) vulnerability in file preview in WeKan before 6.75 allows remote authenticated users to inject arbitrary web script or HTML via names of file attachments. Any user can obtain the privilege to rename within their own board (where they have BoardAdmin access), and renameAttachment does not block XSS payloads.

Wekan, open source kanban board system, between version 3.12 and 4.11, is vulnerable to multiple stored cross-site scripting. This is named 'Fieldbleed' in the vendor's site.

Wekan v6.84 and earlier is vulnerable to Cross Site Scripting (XSS). An attacker with user privilege on kanban board can insert JavaScript code in in "Reaction to comment" feature.

Wekan version 1.04.0 contains a Email / Username Enumeration vulnerability in Register' and 'Forgot your password?' pages that can result in A remote attacker could perform a brute force attack to obtain valid usernames and email addresses.. This attack appear to be exploitable via HTTP Request.

WeKan < 8.19 Attachments Publication Information Disclosure

WeKan < 8.19 Card Comment Author Spoofing via User-controlled authorId

WeKan Position-History Tracking positionHistory.js PositionHistoryBleed authorization

WeKan Meteor Publication cards.js CardPubSubBleed information disclosure

WeKan REST Endpoint boards.js BoardTitleRESTBleed access control

WeKan REST API boards.js setBoardOrgs improper authorization