CVE-2024-47652
Shilpisoft Client Dashboard ≤ 9.7.0
Raw vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2024-47652 is a high-severity Use of Single-factor Authentication (CWE-308) vulnerability in Shilpisoft Client Dashboard. Its CVSS base score is 7.6 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Password Spraying (T1110.003); ranked at the 34th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-2 (Identification and Authentication (Organizational Users)) and IA-8 (Identification and Authentication (Non-organizational Users)) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-42577
Vulnerability Data
This vulnerability exists in Shilpi Client Dashboard due to implementation of inadequate authentication mechanism in the login module wherein access to any users account is granted with just their corresponding mobile number. A remote attacker could exploit this vulnerability by…
more
providing mobile number of targeted user, to obtain complete access to the targeted user account.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.3.4V6.3.6V6.4.2V6.4.3
Mitigating Controls (NIST 800-53 r5) AI
ia-2 requires unique identification and authentication of users, directly stopping single-factor schemes by mandating appropriate (multi-factor) mechanisms.
ia-8 requires unique identification and authentication of non-organizational users, directly stopping single-factor schemes by mandating appropriate (multi-factor) mechanisms.
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.
Explicit MFA requirement directly eliminates single-factor authentication while the control also addresses broader authentication scope.
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.
Secure authentication control explicitly requires multi-factor authentication, directly eliminating single-factor weakness.
Authentication information control directly addresses the need for strong, multi-factor credentials.
Access control policy can mandate multi-factor authentication but does not prescribe the technical implementation.
Access rights provisioning can require MFA, yet the control is broader than authentication strength.
Privileged access rights can be conditioned on MFA, but the control focuses on privilege scope rather than factor count.
Information access restriction can enforce MFA, yet the control is wider than authentication mechanisms.