dbcve.org
Client DashboardApplication · Shilpisoft

CVE-2024-47654

HIGH · 7.5 CVSS v3.1 Published 2024-10-04
Fix available
A fix is available. Upgrade to 9.7.0 or later.
See remediation →
84/100
Remediation priority · High
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 lack of rate limiting and Captcha protection for OTP requests in certain API endpoint. An unauthenticated remote attacker could exploit this vulnerability by sending multiple OTP request through vulnerable API endpoints, which could lead to the OTP bombing on the targeted system.

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 has a vulnerability in its OTP (One-Time Password) API endpoints due to missing rate limiting and CAPTCHA protection. An unauthenticated remote attacker can repeatedly send OTP requests to the vulnerable endpoints, causing OTP bombing (mass SMS/email flooding) against target users.

MitigationImplement rate limiting on OTP request endpoints to restrict the number of requests per user/IP within a time window, and add CAPTCHA protection to OTP request forms to prevent automated attacks.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the installed Shilpisoft Client Dashboard version
    Check the application version in the dashboard footer, admin panel, or by querying the API endpoint such as /api/version. Compare your version number against the affected range: versions prior to 9.7.0 are vulnerable.
    Affected if The installed version is below 9.7.0
  2. Confirm OTP endpoints are accessible
    Identify the OTP request API endpoints in the application, which are commonly /api/otp/send, /api/auth/otp, or similar. Attempt to access these endpoints from an unauthenticated context to verify they are exposed.
    Affected if OTP endpoints are reachable without authentication
  3. Check if rate limiting is configured on OTP endpoints
    Review the web server or application configuration for rate limiting rules targeting OTP endpoints. Inspect middleware or firewall rules that limit requests per IP or user within a time window. Look for directives like limit_req_zone in nginx or similar configurations.
    Affected if No rate limiting rules are found for OTP request endpoints
  4. Verify CAPTCHA protection is enabled on OTP request forms
    Inspect the HTML or frontend code of OTP request pages to check for CAPTCHA implementation such as Google reCAPTCHA, hCaptcha, or custom solutions. Verify that CAPTCHA validation is enforced on the server side for OTP submissions.
    Affected if CAPTCHA is not present or not enforced on OTP request forms

A system is affected if it runs Shilpisoft Client Dashboard version below 9.7.0 and exposes OTP endpoints without rate limiting and CAPTCHA protection.

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 rate limiting on OTP request endpoints to restrict the number of requests per user/IP within a time window, and add CAPTCHA protection to OTP request forms to prevent automated attacks.

Recommended fix Moderate confidence

9.7.0

  1. Upgrade Shilpi Client Dashboard to version 9.7.0 or later to remediate the vulnerability
  2. After upgrading, verify that rate limiting and Captcha protection are enabled for OTP request API endpoints
  3. Test the OTP functionality to confirm the remediation is effective

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

Fix this in Client Dashboard Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47654 — 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-47654 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