# CVE-2024-47657: Improper Access Control Vulnerability

> An authenticated attacker can access other users' sensitive data by manipulating the dfclientid parameter in API requests.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2024
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-74xr-gj9j-429c

## What is CVE-2024-47657?

CVE-2024-47657 is a high-severity missing authorization vulnerability in Shilpi Computers Net Back Office, published on 4 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2024-47657?

It affects 1 product.


Products: Shilpisoft Net Back Office.

## How do I fix CVE-2024-47657?

No fix has been published for CVE-2024-47657 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-47657 being exploited?

There is no known exploitation of CVE-2024-47657 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47657 and fix it if it is affected.

What it is: CVE-2024-47657 is a high-severity missing authorization vulnerability in Shilpi Computers Net Back Office, published on 4 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47657 in the wild and no public exploit code.

Affected product: Shilpi Computers Net Back Office. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-47657/ (Markdown: https://insights.sbomify.com/CVE-2024-47657/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47657
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47657
- OSV: https://osv.dev/vulnerability/CVE-2024-47657

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-47657/
Summaries are generated and may contain mistakes; the official description above is the record.