Nextcloud Server up to 28.0.12/29.0.9/30.0.2 server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Nextcloud Server up to 28.0.12/29.0.9/30.0.2. The affected element is an unknown function. Executing a manipulation can lead to server-side request forgery. The identification of this vulnerability is CVE-2025-47791. The attack may be launched remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Nextcloud Server up to 28.0.12/29.0.9/30.0.2. This vulnerability affects some unknown functionality. The manipulation with an unknown input leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect availability. CVE summarizes:
Nextcloud Server is a self hosted personal cloud system. In Nextcloud Server prior to 28.0.13, 29.0.10, and 30.0.3 and Nextcloud Enterprise Server prior to 28.0.13, 29.0.10, and 30.0.3, a currently unused endpoint to verify a share recipient was not protected correctly, allowing to proxy requests to another server. The endpoint was removed in Nextcloud Server 28.0.13, 29.0.10, and 30.0.3 and Nextcloud Enterprise Server 28.0.13, 29.0.10, and 30.0.3. No known workarounds are available.
The advisory is shared for download at github.com. This vulnerability was named CVE-2025-47791 since 05/09/2025. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available.
Upgrading to version 28.0.13, 29.0.10 or 30.0.3 eliminates this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
- 28.0.0
- 28.0.1
- 28.0.2
- 28.0.3
- 28.0.4
- 28.0.5
- 28.0.6
- 28.0.7
- 28.0.8
- 28.0.9
- 28.0.10
- 28.0.11
- 28.0.12
- 29.0.0
- 29.0.1
- 29.0.2
- 29.0.3
- 29.0.4
- 29.0.5
- 29.0.6
- 29.0.7
- 29.0.8
- 29.0.9
- 30.0.0
- 30.0.1
- 30.0.2
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 4.3
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: Server-side request forgeryCWE: CWE-918
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: Server 28.0.13/29.0.10/30.0.3
Timeline
05/09/2025 🔍05/16/2025 🔍
05/16/2025 🔍
05/16/2025 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2025-47791 (🔍)
GCVE (CVE): GCVE-0-2025-47791
GCVE (VulDB): GCVE-100-309304
Entry
Created: 05/16/2025 16:34Changes: 05/16/2025 16:34 (64)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.