# CVE-2026-5750: Insecure direct object reference (IDOR) vulnerability in Fullstep

> Authenticated users can access and modify other users' personal data and documents via insecure direct object references in the registration API.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/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:** 22 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-27hq-xp89-25mq

## What is CVE-2026-5750?

CVE-2026-5750 is a high-severity missing authorization vulnerability in Fullstep, published on 22 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An insecure direct object reference (IDOR) vulnerability in the Fullstep V5 registration process allows authenticated users to access data belonging to other registered users through various vulnerable authenticated resources in the application. The vulnerable endpoints result from: '/api/suppliers/v1/suppliers//false' to list user information; and '/#/supplier-registration/supplier-registration//2' to update your user information (personal details, documents, etc.).

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

## Which versions are affected by CVE-2026-5750?


## How do I fix CVE-2026-5750?

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

## Is CVE-2026-5750 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5750 and fix it if it is affected.

What it is: CVE-2026-5750 is a high-severity missing authorization vulnerability in Fullstep, published on 22 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5750 in the wild and no public exploit code.

Affected product: Fullstep. 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-2026-5750/ (Markdown: https://insights.sbomify.com/CVE-2026-5750/index.md)
```

## Sources

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

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