dbcve.org
Client DashboardApplication · Shilpisoft

CVE-2024-47652

HIGH · 8.1 CVSS v3.1 Published 2024-10-04
Fix available
A fix is available. Upgrade to 9.7.0 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 providing mobile number of targeted user, to obtain complete access to the targeted user account.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Shilpi Client Dashboard login module implements a critical authentication bypass vulnerability where access to any user account can be obtained solely by providing the user's mobile number, without requiring a password or any secondary authentication factor. This allows a remote attacker to achieve complete account takeover of any targeted user.

MitigationImplement proper multi-factor authentication requiring both mobile number AND password, or implement proper session token-based authentication with secure credential validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Client DashboardApplication
Affected:< 9.7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Shilpisoft Client Dashboard version
    Check the application's version information through the admin panel, about page, or by querying the application binaries/configuration files for version metadata
    Affected if the installed version is below 9.7.0
  2. Examine login module authentication configuration
    Review the login module's configuration files or settings to determine what credentials are required for authentication (mobile number only, password, or both)
    Affected if the login module accepts authentication with mobile number alone without requiring a password or secondary factor
  3. Verify if mobile-number-only login is functional
    Attempt to initiate a login using a valid mobile number without providing a password, observing whether the system grants access or accepts the request
    Affected if the system permits login access using only a mobile number without password validation
  4. Review authentication session handling
    Inspect how the application handles sessions after login attempts, checking whether valid sessions are created without proper credential verification
    Affected if the application creates authenticated sessions for mobile-number-only requests without validating additional credentials

You are affected if Shilpisoft Client Dashboard is installed at a version below 9.7.0 AND the login module permits access using only a mobile number without password verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.7.0 or later
Fixed in 9.7.0
Interim mitigation

Implement proper multi-factor authentication requiring both mobile number AND password, or implement proper session token-based authentication with secure credential validation.

Recommended fix High confidence

9.7.0 or later

  1. Upgrade Shilpi Client Dashboard to version 9.7.0 or later
  2. After upgrading, verify that the login module now requires proper authentication (username/password or other multi-factor credentials) in addition to mobile number
  3. Confirm that mobile number alone no longer grants access to user accounts
  4. As a defense-in-depth measure, ensure multi-factor authentication is enabled if supported by the application

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Client Dashboard Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47652 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47652 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data