CVE-2024-50488
Published: 28 October 2024
Summary
CVE-2024-50488 is a high-severity Authentication Bypass Using an Alternate Path or Channel (CWE-288) vulnerability in Priyabratasarkar Token Login. Its CVSS base score is 8.8 (High).
Operationally, ranked in the top 3.6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
The Token Login plugin for WordPress, authored by yespbs and present in versions up to and including 1.0.3, is affected by an authentication bypass vulnerability tracked as CVE-2024-50488. The flaw arises from missing authentication checks that can be circumvented via an alternate path or channel, corresponding to CWE-288 and CWE-306, and carries a CVSS 3.1 base score of 8.8.
An attacker with low privileges can exploit the issue over the network without user interaction to bypass authentication entirely, resulting in high impacts to confidentiality, integrity, and availability on the affected WordPress site.
The issue is catalogued in the Patchstack advisory, which identifies the broken authentication condition in the plugin and points to the need for an update beyond version 1.0.3.
The associated EPSS score reached a peak of 0.3854 after disclosure, reflecting a material increase in exploitation interest that warrants renewed attention.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-44914
Vulnerability details
Authentication Bypass Using an Alternate Path or Channel vulnerability in yespbs Token Login token-login allows Authentication Bypass.This issue affects Token Login: from n/a through <= 1.0.3.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Mandates additional authentication for access under defined conditions, ensuring critical or high-risk functions are not left without authentication.
Identity providers mandate authentication for functions that would otherwise lack it.
Requires authentication for non-organizational users, preventing access to critical functions without proper identification and authentication.
Requires established identification and authentication to unlock, mitigating missing authentication for continued system access.
Requiring identification and rationale for actions allowed without authentication ensures critical functions are not left unprotected by forcing review of authentication requirements.
Authorizing remote access reduces the ability to bypass authentication via unauthorized alternate remote channels.
Authorizing mobile device connections to organizational systems ensures authentication is performed for this critical access function.
Guarantees critical functions are protected by mandatory invocation of the access control mechanism.