CVE-2024-50488
Auth Bypass in Priyabratasarkar Token Login ≤ 1.0.3
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
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, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked in the top 40% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-14 (Permitted Actions Without Identification or Authentication) and AC-25 (Reference Monitor) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
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.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-44914
Vulnerability Data
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
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 13 hardening rules · 4 OS baselines
V6.4.3V6.6.1V12.1.3V6.2.3
Mitigating Controls (NIST 800-53 r5) AI
Requires a tamperproof, always-invoked reference monitor that structurally blocks bypass via any alternate path.
Enforces authorization checks on every logical access path, eliminating unauthenticated alternate channels.
Directly mandates unique identification and authentication of users before access to functions requiring identity.
Extends the same authentication requirement to non-organizational users accessing critical functionality.
Requires authentication of services before they can invoke or expose critical functions.
Explicitly identifies and limits actions permitted without authentication, preventing critical functions from being exposed.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Managing identities and credentials is a prerequisite for authentication but does not itself enforce it on critical functions.
Requiring authentication on every channel and path directly eliminates alternate-path bypasses.
Enforcing authorizations and least privilege across all access vectors prevents unauthenticated alternate paths.
Protecting networks and environments from unauthorized logical access blocks bypass via undocumented channels.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.5.15 only requires defining a topic-specific access control policy and determining requirements; it does not itself enforce, implement or configure any access rules that would stop an alternate unauthenticated path from being exploitable.
Access rights provisioning and review prevent bypass via unmonitored or alternate channels.
Mandating authentication requirements for critical functions at the requirements-gathering stage ensures that essential operations are not left unprotected by missing login or verification mechanisms.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Oracle Linux 8 (3 rules)
- V-248598 There must be no ".shosts" files on the OL 8 operating system. blocks CWE-288
- V-248827 OL 8 must not have the rsh-server package installed. blocks CWE-288, CWE-306
- V-248585 OL 8 must require reauthentication when using the "sudo" command. blocks CWE-306
Oracle Linux 9 (2 rules)
- V-271757 OL 9 file systems must not contain shosts.equiv files. blocks CWE-288
- V-271758 OL 9 file systems must not contain .shosts files. blocks CWE-288
RHEL 7 (4 rules)
- V-204440 Red Hat Enterprise Linux operating systems version 7.2 or newer using Unified Extensible Firmware Interface (UEFI) must require authentication upon booting into single-user and maintenance modes. blocks CWE-288
- V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. blocks CWE-288, CWE-306
- V-204424 The Red Hat Enterprise Linux operating system must not allow accounts configured with blank or null passwords. blocks CWE-288
RHEL 8 (2 rules)
- V-230492 RHEL 8 must not have the rsh-server package installed. blocks CWE-306
- V-237643 RHEL 8 must require re-authentication when using the "sudo" command. blocks CWE-306