Logto up to 1.37.1 experience-interaction.ts single-factor authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 3.35 |
Summary
A vulnerability was found in Logto up to 1.37.1. It has been rated as critical. This affects an unknown function of the file packages/core/src/routes/experience/classes/experience-interaction.ts. This manipulation causes use of single-factor authentication. This vulnerability appears as CVE-2026-15616. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability classified as critical was found in Logto up to 1.37.1. Affected by this vulnerability is an unknown function of the file packages/core/src/routes/experience/classes/experience-interaction.ts. The manipulation with an unknown input leads to a use of single-factor authentication vulnerability. The CWE definition for the vulnerability is CWE-308. The use of single-factor authentication can lead to unnecessary risk of compromise when compared with the benefits of a dual-factor authentication scheme. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Logto does not enforce locally configured MFA during SSO authentication, allowing users to bypass second-factor requirements and grants unauthorized access.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-15616 since 07/13/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/23/2026). MITRE ATT&CK project uses the attack technique T1111 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Use of single-factor authenticationCWE: CWE-308 / CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
07/13/2026 CVE reserved07/23/2026 Advisory disclosed
07/23/2026 VulDB entry created
07/23/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2026-15616 (🔒)
GCVE (CVE): GCVE-0-2026-15616
GCVE (VulDB): GCVE-100-382753
Entry
Created: 07/23/2026 18:33Changes: 07/23/2026 18:33 (51)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.