dbcve.org
Net Back OfficeApplication · Shilpisoft

CVE-2024-47657

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-04
Fix available
A fix is available. Upgrade to 5.5.002 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 the Shilpi Net Back Office due to improper access controls on certain API endpoints. An authenticated remote attacker could exploit this vulnerability by manipulating a parameter dfclientid through API request URLs which could lead to unauthorized access to sensitive information belonging to 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 Net Back Office where authenticated users can access other users' sensitive data by manipulating the dfclientid parameter in API requests. The application fails to verify that the authenticated user has proper authorization to access the requested client data.

MitigationImplement proper object-level authorization checks on all API endpoints to verify the authenticated user owns or has permission to access the requested dfclientid resource before returning any data.

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
Net Back OfficeApplication
Affected:< 5.5.002

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Verify Shilpisoft Net Back Office version
    Locate the application version information in the software's about panel, installation directory, or by querying the application's built-in version endpoint. Common locations include the login page footer, help menu, or a /version API endpoint.
    Affected if The installed version is lower than 5.5.002 (e.g., 5.5.001, 5.5.000, or earlier releases).
  2. Identify exposed API endpoints accepting dfclientid
    Review application API documentation, intercept HTTP traffic during normal operation, or scan for endpoints that accept the dfclientid parameter in URLs or request bodies. Look for patterns like /api/client/*, /api/dfclientid/*, or similar client data retrieval paths.
    Affected if The API endpoint accepting the dfclientid parameter is publicly accessible or accessible to authenticated users without proper segmentation.
  3. Test authorization enforcement on client data endpoints
    Log in as a standard authenticated user, then attempt to access another user's client data by modifying the dfclientid parameter value in API requests. Compare the response when using your own valid dfclientid versus a different user's dfclientid value.
    Affected if The API returns sensitive data for a dfclientid that does not belong to the authenticated user, indicating missing authorization checks.
  4. Review server-side authorization logic
    Examine the server-side code or configuration for the client data API endpoint. Locate the handler that processes dfclientid parameter requests and verify whether an ownership or permission validation function is executed before returning data.
    Affected if No code or logic exists to verify that the authenticated user owns or has permission to access the requested dfclientid resource.

You are affected if your installed version is below 5.5.002 and the API endpoint accepting dfclientid returns data for users who do not own the requested client record.

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 5.5.002 or later
Fixed in 5.5.002
Interim mitigation

Implement proper object-level authorization checks on all API endpoints to verify the authenticated user owns or has permission to access the requested dfclientid resource before returning any data.

Recommended fix Moderate confidence

Net Back Office 5.5.002

  1. 1. Back up the current Net Back Office installation and database
  2. 2. Download Net Back Office version 5.5.002 from the official vendor
  3. 3. Install the version 5.5.002 update following standard vendor installation procedures
  4. 4. Verify the installation completed successfully
  5. 5. Test that the dfclientid parameter is now properly validated and access controls are enforced

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

Fix this in Net Back Office 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-47657 — 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-47657 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