Critical

Sensitive User Document Exposure in Wekan notificationUsers Publication

IdentifiersCVE-2026-30847CWE-200· Exposure of Sensitive Information…

CVE-2026-30847 is an information disclosure vulnerability in Wekan, an open source kanban application built on Meteor. In Wekan versions 8.31.0 through 8.33, the custom notificationUsers publication returns user documents without field-level filtering. As a result, the ReactiveCache.getUsers() call exposes complete user records to subscribers rather than a restricted subset of safe attributes. The exposed data can include highly sensitive fields such as bcrypt password hashes, active session login tokens, email verification tokens, full email addresses, and stored OAuth tokens. Because Meteor custom publications return all fields present in the cursor unless explicitly filtered, any authenticated user able to trigger this publication can retrieve sensitive data belonging to other users.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authenticated attacker to collect sensitive account data for other users at scale. Exposure of password hashes can enable offline cracking attempts, while disclosure of active session tokens can support session hijacking. Exposure of email verification tokens and OAuth tokens can further facilitate unauthorized account actions and broader account compromise. The overall impact is loss of confidentiality for user secrets and a realistic path to full account takeover of affected users.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to the affected instance to trusted users only and minimize the number of authenticated accounts that can access the application. Monitor for suspicious account activity consistent with token abuse or account takeover, rotate active session tokens, revoke and reissue OAuth tokens where applicable, and require password resets for potentially exposed accounts. Additional defensive review of client-accessible publications and removal of unnecessary sensitive data from user documents can reduce exposure.

Remediation

Patch, then assume compromise.

Upgrade Wekan to version 8.34 or later, where the issue is fixed. The vulnerable publication should return only explicitly allowlisted user fields required for application functionality, and sensitive fields associated with authentication, sessions, email verification, and external identity providers should never be published to clients. Review other custom Meteor publications in the application for similar missing field restrictions.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

Wekan ProjectWekanapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

3 SOURCESView more in app

bugflationNews

May 6, 2026

GitHub Taskflow Agent produces 18 public CVEs across eight projects - Bugflation

A GitHub Security Lab-reported vulnerability affecting Wekan; the content only indicates it is part of a set of CVEs dominated by access-control and web-application logic defects.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2