# CVE-2026-30845: Wekan Exposes Sensitive Data through Lack of Field Filtering During Board Publication

> Attackers can retrieve sensitive webhook credentials from public or member-accessible boards, enabling unauthorized actions in external services.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2026
- **Updated:** 9 Mar 2026

## What is CVE-2026-30845?

CVE-2026-30845 is a medium-severity vulnerability in Wekan, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Wekan is an open source kanban tool built with Meteor. In versions 8.31.0 through 8.33, the board composite publication in Wekan publishes all integration data for a board without any field filtering, exposing sensitive fields including webhook URLs and authentication tokens to any subscriber. Since board publications are accessible to all board members regardless of their role (including read-only and comment-only users), and even to unauthenticated DDP clients for public boards, any user who can access a board can retrieve its webhook credentials. This token leak allows attackers to make unauthenticated requests to the exposed webhooks, potentially triggering unauthorized actions in connected external services. This issue has been fixed in version 8.34.

Weakness: CWE-862 (Missing Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-30845?

It affects 1 product.


Products: Wekan Project Wekan.

## How do I fix CVE-2026-30845?

No fix has been published for CVE-2026-30845 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-30845 being exploited?

There is no known exploitation of CVE-2026-30845 in the wild and no public exploit code.

## Other vulnerabilities in Wekan

- [CVE-2026-30843](https://insights.sbomify.com/CVE-2026-30843/): Wekan has Cross-Board IDOR in Custom Fields Update Endpoints (critical 9.3)
- [CVE-2026-30844](https://insights.sbomify.com/CVE-2026-30844/): Wekan Vulnerable to SSRF through Lack of Validation or Filtering in Attachment URL Loading (critical 9.3)
- [CVE-2026-30847](https://insights.sbomify.com/CVE-2026-30847/): Wekan Credential Leak via notificationUsers Publication Exposes Password Hashes and Session Tokens (critical 9.3)
- [CVE-2025-65780](https://insights.sbomify.com/CVE-2025-65780/): Missing authorization in n/a (high 8.8)
- [CVE-2026-30846](https://insights.sbomify.com/CVE-2026-30846/): Wekan Exposes All Global Webhook Integrations through globalwebhooks Publication (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30845 and fix it if it is affected.

What it is: CVE-2026-30845 is a medium-severity vulnerability in Wekan, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-30845 in the wild and no public exploit code.

Affected product: Wekan. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-30845/ (Markdown: https://insights.sbomify.com/CVE-2026-30845/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-30845
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-30845
- OSV: https://osv.dev/vulnerability/CVE-2026-30845

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-30845/
Summaries are generated and may contain mistakes; the official description above is the record.