Categories
CVE-2025-65782 medium CVSS 6.5

Vulnerability in Wekan The Open Source kanban board system (CVE-2025-65782)

Summary

Vulnerability in Wekan The Open Source kanban board system (CVE-2025-65782). Data can be tampered with by attackers. Mitigation: upgrade to 18.16 or later.

Original description

The description as published by the source.

An issue was discovered in Wekan The Open Source kanban board system up to version 18.15, fixed in 18.16. Authorization flaw in card update handling allows board members (and potentially other authenticated users) to add/remove arbitrary user IDs in vote.positive / vote.negative arrays, enabling vote forgery and unauthorized voting.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-65782 has been found in Wekan The Open Source kanban board system.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade Wekan The Open Source kanban board system to 18.16 or later.
If unsure, ask your IT team or search "Wekan The Open Source kanban board system CVE-2025-65782" on the vendor's site.

CVE-2025-65782 (Wekan The Open Source kanban board system) — CWE-285 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 18.16 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-285) exists in Wekan The Open Source kanban board system.

📍 Affected scope

Check the vendor advisory for the affected versions of Wekan The Open Source kanban board system.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 18.16.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Wekan The Open Source kanban board system を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade Wekan The Open Source kanban board system to 18.16

    ステージング環境で 18.16 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details