Wekan exposes sensitive user data in versions 8.31.0 through 8.33

Summary

Wekan's notification system exposes sensitive user data, including passwords and login tokens, making it possible for attackers to steal credentials and take control of user accounts. This affects all users who have triggered the notification system in Wekan versions 8.31.0 through 8.33. Update to version 8.34 to fix this issue.

What to do

No fix is available yet. Check with your software vendor for updates.

Affected software

Vendor	Product	Affected versions	Fix available
wekan_project	wekan	> 8.31 , <= 8.33	–

Original title

Wekan is an open source kanban tool built with Meteor. In versions 8.31.0 through 8.33, the notificationUsers publication in Wekan publishes user documents with no field filtering, causing the Reac...

Original description

Wekan is an open source kanban tool built with Meteor. In versions 8.31.0 through 8.33, the notificationUsers publication in Wekan publishes user documents with no field filtering, causing the ReactiveCache.getUsers() call to return all fields including highly sensitive data such as bcrypt password hashes, active session login tokens, email verification tokens, full email addresses, and any stored OAuth tokens. Unlike Meteor's default auto-publication which strips the services field for security, custom publications return whatever fields the cursor contains, meaning all subscribers receive the complete user documents. Any authenticated user who triggers this publication can harvest credentials and active session tokens for other users, enabling password cracking, session hijacking, and full account takeover. This issue has been fixed in version 8.34.

nvd CVSS4.0 9.3

Vulnerability type

CWE-200 Information Exposure

CWE-285 Improper Authorization