Security readout for executives and security teams
Plain-English summary
CVE-2018-19391 is a stored cross-site scripting issue in Cobham Satcom SAILOR 250 and 500 devices before firmware 1.25. An unauthenticated attacker could place malicious content in a phone book name field, causing later browser-side execution when viewed.
Executive priority
Prioritize remediation for exposed or shared-management satcom devices because the issue is unauthenticated and stored. It is not KEV-listed and has no supplied CVSS score, so urgency should be driven by device exposure and operational reliance.
Technical view
The CVE describes persistent XSS reachable through the device web interface's phone book name field. Sources identify SAILOR 250 and 500 devices before version 1.25. No CVSS score, CWE mapping, vendor advisory, or authoritative exploit-in-the-wild confirmation is provided in the bundle.
Likely exposure
Exposure is likely limited to organizations operating Cobham Satcom SAILOR 250 or 500 devices below firmware 1.25, especially where the management interface is reachable by untrusted users or networks. The source bundle does not provide CPEs or a complete affected-version matrix.
Exploitation context
The CVE record says exploitation can be unauthenticated and persistent through a phone book field. KEV is false, and the supplied sources do not establish active exploitation in the wild. Public researcher references exist, so treat the issue as publicly documented.
Researcher notes
The evidence is narrow: public CVE metadata and researcher references identify the product family, version boundary, and vulnerable field. The bundle lacks CVSS, CPEs, official vendor remediation text, and exploitation telemetry, so avoid broad claims beyond SAILOR 250/500 before 1.25.
Mitigation direction
- Inventory Cobham Satcom SAILOR 250 and 500 devices.
- Check current firmware against version 1.25.
- Update to 1.25 or later where vendor guidance supports it.
- Restrict device management interfaces to trusted administrative networks.
- Review vendor or maintainer advisories for model-specific remediation details.
Validation and detection
- Confirm whether SAILOR 250 or 500 devices are in use.
- Record firmware versions and compare with the pre-1.25 affected range.
- Verify management interfaces are not exposed to untrusted networks.
- Review phone book entries for unexpected markup or script-like content.
- Check administrative access logs for unusual unauthenticated changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-19391 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://cyberskr.com/blog/cobham-satcom-250-500.htmlCVE reference · x_refsource_MISC
- https://gist.github.com/CyberSKR/f6fc93702b9b9b73afa07877d1479fe0CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.