Nextcloud Server up to 29.0.14/30.0.8/31.0.2 config.php remember_login_cookie_lifetime improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Nextcloud Server up to 29.0.14/30.0.8/31.0.2 and classified as critical. This issue affects some unknown processing of the file config.php. Performing a manipulation of the argument remember_login_cookie_lifetime results in improper authentication. This vulnerability is identified as CVE-2025-47790. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability was found in Nextcloud Server up to 29.0.14/30.0.8/31.0.2. It has been classified as critical. This affects an unknown part of the file config.php. The manipulation of the argument remember_login_cookie_lifetime with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Nextcloud Server is a self hosted personal cloud system. Nextcloud Server prior to 29.0.15, 30.0.9, and 31.0.3 and Nextcloud Enterprise Server prior to 26.0.13.15, 27.1.11.15, 28.0.14.6, 29.0.15, 30.0.9, and 31.0.3 have a bug with session handling. The bug caused skipping the second factor confirmation after a successful login with the username and password when the server was configured with `remember_login_cookie_lifetime` set to `0`, once the session expired on the page to select the second factor and the page is reloaded. Nextcloud Server 29.0.15, 30.0.9, and 31.0.3 and Nextcloud Enterprise Server is upgraded to 26.0.13.15, 27.1.11.15, 28.0.14.6, 29.0.15, 30.0.9 and 31.0.3 contain a patch. As a workaround, set the `remember_login_cookie_lifetime` in config.php to a value other than `0`, e.g. `900`. Beware that this is only a workaround for new sessions created after the configuration change. System administration can delete affected sessions.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2025-47790 since 05/09/2025. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
By approaching the search of inurl:config.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 26.0.13.15, 27.1.11.15, 28.0.14.6, 29.0.15, 30.0.9 or 31.0.3 eliminates this vulnerability. Applying a patch 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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 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
- 29.0.10
- 29.0.11
- 29.0.12
- 29.0.13
- 29.0.14
- 30.0.0
- 30.0.1
- 30.0.2
- 30.0.3
- 30.0.4
- 30.0.5
- 30.0.6
- 30.0.7
- 30.0.8
- 31.0.0
- 31.0.1
- 31.0.2
License
Website
- Product: https://github.com/nextcloud/server/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 5.9
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.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: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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 26.0.13.15/27.1.11.15/28.0.14.6/29.0.15/30.0.9/31.0.3
Patch: github.com
Timeline
05/09/2025 🔍05/16/2025 🔍
05/16/2025 🔍
10/01/2025 🔍
Sources
Product: github.comAdvisory: GHSA-9h3w-f3h4-qqrh
Status: Confirmed
CVE: CVE-2025-47790 (🔍)
GCVE (CVE): GCVE-0-2025-47790
GCVE (VulDB): GCVE-100-309291
Entry
Created: 05/16/2025 16:25Updated: 10/01/2025 01:34
Changes: 05/16/2025 16:25 (68), 10/01/2025 01:34 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.