Authentication Bypass in Wekan The Open Source kanban board system (CVE-2025-65781)
Summary
Authentication bypass in Wekan The Open Source kanban board system (CVE-2025-65781). Risk of unauthorized operations or information disclosure. 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. Attachment upload API treats the Authorization bearer value as a userId and enters a non-terminating body-handling branch for any non-empty bearer token, enabling trivial application-layer DoS and latent identity-spoofing.
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-65781 has been found in Wekan The Open Source kanban board system.
Risk of unauthorized operations or information disclosure. CVSS score: 8.2/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-65781" on the vendor's site.
CVE-2025-65781 (Wekan The Open Source kanban board system) — CWE-287 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / 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.
Authentication bypass (CWE-287) exists in Wekan The Open Source kanban board system.
Check the vendor advisory for the affected versions of Wekan The Open Source kanban board system.
Severity: High (CVSS 8.2/10). Risk of unauthorized operations or information disclosure.
Update to 18.16.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Wekan The Open Source kanban board system を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Wekan The Open Source kanban board system to 18.16ステージング環境で 18.16 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch cve@mitre.org
- patch cve@mitre.org
- web cve@mitre.org
- web cve@mitre.org