Philips SureSigns VS4 Improper Access Control

published 2020-08-21 6y ago modified 2026-06-17 4mo ago also EUVD-2020-8207

cvss: 6.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits: 0; none known

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

Patch / fix

fixed in 1

Philips SureSigns VS4 A.07.107

Is CVE-2020-16241 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.3	CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H
NVD	3.1	2.1	CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:N/I:N/A:P

Affected products

Philips SureSigns VS4

Classification

Weakness

CWE-284 Improper Access Control
CWE-863 Incorrect Authorization

References

us-cert.cisa.gov /ics/advisories/icsma-20-233-01
third-party-advisory, us-government-resource
philips.com /a-w/security/security-advisories/product-security-2020.html#2020_archive

Sources

CVE List CVE-2020-16241
NVD CVE-2020-16241

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.