| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Nextcloud Deck up to 1.14.5/1.15.1. It has been classified as critical. The affected element is an unknown function. This manipulation causes access control. The identification of this vulnerability is CVE-2025-66557. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability classified as critical was found in Nextcloud Deck up to 1.14.5/1.15.1. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is known as CVE-2025-66557 since 12/04/2025. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 1.14.6 or 1.15.2 eliminates this vulnerability. Applying the patch f1da8b30a455f02373d44154da04494c949a95ae is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-2757). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Nextcloud Nextcloud
Product
Type
Vendor
Name
Version
License
Website
- Product: https://github.com/nextcloud/deck/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔒
CNA Base Score: 5.4
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Deck 1.14.6/1.15.2
Patch: f1da8b30a455f02373d44154da04494c949a95ae
Timeline
12/04/2025 CVE reserved12/06/2025 Advisory disclosed
12/06/2025 VulDB entry created
12/09/2025 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-wwr8-hx9g-rjvv
Status: Confirmed
CVE: CVE-2025-66557 (🔒)
GCVE (CVE): GCVE-0-2025-66557
GCVE (VulDB): GCVE-100-334549
CERT Bund: WID-SEC-2025-2757 - Nextcloud (Contacts, Talk, Deck und Twofactor WebAuthn): Mehrere Schwachstellen
Entry
Created: 12/06/2025 05:00Updated: 12/09/2025 22:27
Changes: 12/06/2025 05:00 (67), 12/08/2025 16:46 (7), 12/09/2025 22:27 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.