# CVE-2025-0783: pankajindevops scale API Endpoint access control

> Remote attackers can bypass access controls on the API endpoint of pankajindevops scale due to improper authorization checks.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/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:** 28 Jan 2025
- **Updated:** 28 Jan 2025
- **Also known as:** GHSA-cwp3-3mxc-v33w

## What is CVE-2025-0783?

CVE-2025-0783 is a medium-severity missing authorization vulnerability in pankajindevops scale, published on 28 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, was found in pankajindevops scale up to 20241113. This affects an unknown part of the component API Endpoint. The manipulation leads to improper access controls. It is possible to initiate the attack remotely. This product does not use versioning. This is why information about affected and unaffected releases are unavailable.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2025-0783?


## How do I fix CVE-2025-0783?

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

## Is CVE-2025-0783 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-0783 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0783 and fix it if it is affected.

What it is: CVE-2025-0783 is a medium-severity missing authorization vulnerability in pankajindevops scale, published on 28 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-0783 exists.

Affected product: pankajindevops scale. 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-2025-0783/ (Markdown: https://insights.sbomify.com/CVE-2025-0783/index.md)
```

## Sources

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

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