Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 19 Nov 2025 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:librechat:librechat:0.7.9:-:*:*:*:*:*:* | |
| Metrics |
cvssV3_1
|
Wed, 05 Nov 2025 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 31 Oct 2025 10:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Librechat
Librechat librechat |
|
| Vendors & Products |
Librechat
Librechat librechat |
Thu, 30 Oct 2025 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In danny-avila/librechat version 0.7.9, there is an insecure API design issue in the 2-Factor Authentication (2FA) flow. The system allows users to disable 2FA without requiring a valid OTP or backup code, bypassing the intended verification process. This vulnerability occurs because the backend does not properly validate the OTP or backup code when the API endpoint '/api/auth/2fa/disable' is directly accessed. This flaw can be exploited by authenticated users to weaken the security of their own accounts, although it does not lead to full account compromise. | |
| Title | Insecure API Design in danny-avila/librechat | |
| Weaknesses | CWE-440 | |
| References |
| |
| Metrics |
cvssV3_0
|
Status: PUBLISHED
Assigner: @huntr_ai
Published:
Updated: 2025-11-05T14:57:26.783Z
Reserved: 2025-08-10T19:01:03.291Z
Link: CVE-2025-8850
Updated: 2025-11-05T14:57:23.631Z
Status : Analyzed
Published: 2025-10-30T20:15:39.633
Modified: 2025-11-19T15:27:48.057
Link: CVE-2025-8850
No data.
OpenCVE Enrichment
Updated: 2025-10-31T10:13:55Z