Insecure API Design in danny-avila/librechat
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| danny-avila | danny-avila/librechat | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Librechat | Librechat | — |
No CVSS v4.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.408% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:librechat:librechat:0.7.9:-:*:*:*:*:*:* | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Librechat
Librechat librechat |
|
| Vendors & Products |
Librechat
Librechat librechat |
| 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
|