CVE-2026-30843 is an insecure direct object reference vulnerability in Wekan, an open source kanban application built with Meteor. Affected versions 8.32 and 8.33 improperly authorize operations on custom fields associated with boards. The vulnerable PUT endpoint for board custom fields validates that the authenticated user has access to the board identified in the request path, but the subsequent database update filters only on the custom field identifier and does not verify that the targeted custom field actually belongs to that board. As a result, authorization is checked against one resource while the modification is applied to another. The same authorization flaw also affects the POST, PUT, and DELETE endpoints used to manage dropdown items under custom fields. An attacker who controls or has access to any board can supply the identifier of a custom field belonging to a different board and modify it across board boundaries. The issue enables unauthorized cross-board manipulation of custom field data.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.