dbcve.org
Client DashboardApplication · Shilpisoft

CVE-2024-47653

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-04
Fix available
A fix is available. Upgrade to 9.7.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 authorization for modification and cancellation requests through certain API endpoints. An authenticated remote attacker could exploit this vulnerability by placing or cancelling requests through API request body leading to unauthorized modification of requests belonging to the other users.

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 · moderate confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in Shilpi Client Dashboard where API endpoints for modification and cancellation requests lack proper authorization checks. An authenticated attacker can manipulate the API request body to modify or cancel requests belonging to other users, achieving horizontal privilege escalation.

MitigationImplement proper authorization validation on all modification and cancellation API endpoints to verify that the authenticated user owns the request before allowing any changes. Additionally, use indirect object references and enforce strict access control checks.

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

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

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 version of Shilpisoft Client Dashboard
    Check the application version displayed in the dashboard UI, typically found in the About section, settings menu, or footer. Alternatively, check version files in the application installation directory if accessible.
    Affected if The installed version is lower than 9.7.0 (e.g., 9.6.x, 9.5.x, etc.)
  2. Verify API endpoints for modification requests are accessible
    Locate the API endpoint paths for modifying requests (e.g., /api/requests/{id}/modify or similar). Test if these endpoints accept POST/PUT requests with a request ID parameter in the URL or body.
    Affected if The modification endpoint accepts requests where the ID parameter references another user's request and processes the request without additional authorization headers or tokens beyond basic authentication.
  3. Verify API endpoints for cancellation requests are accessible
    Locate the API endpoint paths for canceling requests (e.g., /api/requests/{id}/cancel or similar). Test if these endpoints accept DELETE or POST requests with a request ID parameter.
    Affected if The cancellation endpoint accepts requests where the ID parameter references another user's request and completes the cancellation without verifying ownership.
  4. Inspect authorization logic on affected endpoints
    Review the server-side code or API configuration for modification and cancellation endpoints. Check if the code verifies that the authenticated user's ID matches the owner of the request being modified or canceled.
    Affected if The endpoints lack ownership verification logic, or the code only checks for a valid authenticated session without validating that the user has permission to act on the specific request ID.

A user is affected if their Shilpisoft Client Dashboard installation is version 9.6.x or lower AND the modification/cancellation API endpoints do not validate that the authenticated user owns the request being modified or canceled.

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 authorization validation on all modification and cancellation API endpoints to verify that the authenticated user owns the request before allowing any changes. Additionally, use indirect object references and enforce strict access control checks.

Recommended fix High confidence

9.7.0

  1. 1. Identify the current version of Shilpi Client Dashboard installed in your environment
  2. 2. Download Shilpi Client Dashboard version 9.7.0 or later from the official vendor source
  3. 3. Back up the current installation including configuration files and database
  4. 4. Stop the Shilpi Client Dashboard service
  5. 5. Install version 9.7.0 following standard upgrade procedures
  6. 6. Start the Shilpi Client Dashboard service
  7. 7. Verify the upgrade was successful by checking the version number
  8. 8. Test that API endpoints for modification and cancellation requests now properly enforce authorization (users should only be able to modify/cancel their own requests)

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

Fix this in Client Dashboard Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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