Vulnerability in Nextcloud Deck (CVE-2025-66557)
Summary
Vulnerability in Nextcloud Deck (CVE-2025-66557). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.14.6 or later.
Original description
The description as published by the source.
Nextcloud Deck is a kanban style organization tool aimed at personal planning and project organization for teams integrated with Nextcloud. Prior to 1.14.6 and 1.15.2, a bug in the permission logic allowed users with "Can share" permission to modify the permissions of other recipients. This vulnerability is fixed in 1.14.6 and 1.15.2.
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-66557 has been found in Nextcloud Deck.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade Nextcloud Deck to 1.14.6 or later.
If unsure, ask your IT team or search "Nextcloud Deck CVE-2025-66557" on the vendor's site.
CVE-2025-66557 (Nextcloud Deck) — CWE-284 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.14.6 — 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.
A vulnerability (CWE-284) exists in Nextcloud Deck.
Check the vendor advisory for the affected versions of Nextcloud Deck.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 1.14.6.
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・依存マニフェストで Nextcloud Deck を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Nextcloud Deck to 1.14.6ステージング環境で 1.14.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。