Categories
CVE-2025-66545 low CVSS 3.5

Vulnerability in Nextcloud (CVE-2025-66545)

Summary

Vulnerability in Nextcloud (CVE-2025-66545). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 14.0.11 or later.

Original description

The description as published by the source.

Nextcloud Groupfolders provides admin-configured folders shared by everyone in a group or team. Prior to 14.0.11, 15.3.12, 16.0.15, 17.0.14, 18.1.8, 19.1.8, and 20.1.2, a user with read-only permission can restore a file from the trash bin. This vulnerability is fixed in 14.0.11, 15.3.12, 16.0.15, 17.0.14, 18.1.8, 19.1.8, and 20.1.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-66545 has been found in Nextcloud.
Risk of unauthorized operations or information disclosure. CVSS score: 3.5/10.
What to do: upgrade Nextcloud to 14.0.11 or later.
If unsure, ask your IT team or search "Nextcloud CVE-2025-66545" on the vendor's site.

CVE-2025-66545 (Nextcloud) — CWE-707 / CVSS v3 3.5
Attack vector: remote (network-reachable)
Patched: 14.0.11 — 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-707) exists in Nextcloud.

📍 Affected scope

Check the vendor advisory for the affected versions of Nextcloud.

🔥 Severity

Severity: Low (CVSS 3.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 14.0.11.

🛡️ 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. Run grep -r 'Nextcloud' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

  1. 1
    Identify exposure identify
    grep -r 'Nextcloud' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Nextcloud を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade Nextcloud to 14.0.11

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

  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