Is this vulnerability remotely exploitable?

Yes. Any remote client that can connect to the Wekan instance and subscribe to a vulnerable board publication—either as a board member or as an unauthenticated user on public boards—can retrieve the exposed integration data.

What level of access is required to exploit it?

For private boards, any board membership is sufficient, including read-only and comment-only roles. For public boards, an attacker may not need any authenticated account at all, only the ability to act as a DDP client.

What is the safest general fix pattern?

The safest pattern is to explicitly project only non-sensitive fields in all publications, completely exclude tokens and webhook secrets from client-facing data flows, and move any necessary secret handling into server-side or privileged-only APIs.

Severity:

HIGH RISK

(8.2)

Sensitive Data Exposure via Insecure Publication (CWE-200) in Wekan Board Integrations

CVE-2026-30845

Published:

Mar 6, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Sensitive Data Exposure

CWE:

CWE-200;CWE-862

Impact:

Credential Disclosure Leading to Unauthorized Actions in External Services

Severity:

HIGH RISK

(8.2)

CVSS Version:

3.1

Vulnerability Type

Category:

Sensitive Data Exposure

CWE:

CWE-200;CWE-862

Impact:

Credential Disclosure Leading to Unauthorized Actions in External Services

Severity:

HIGH RISK

(8.2)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Sensitive Data Exposure via Insecure Publication (CWE-200) in Wekan Board Integrations

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal