Winston 1.5.4 devices do not enforce authorization.

published 2020-10-28 6y ago modified 2026-06-17 4mo ago also EUVD-2020-8221

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 61%
public exploits: 0; none known

Winston 1.5.4 devices do not enforce authorization. This is exploitable from the intranet, and can be combined with other vulnerabilities for remote exploitation.

Is CVE-2020-16260 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.93% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

labs.bishopfox.com https://labs.bishopfox.com/advisories/winston-privacy-version-1.5.4 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness

CWE-862 Missing Authorization

References

labs.bishopfox.com /advisories/winston-privacy-version-1.5.4
exploit, third-party-advisory
winstonprivacy.com /
product

Sources

CVE List CVE-2020-16260
NVD CVE-2020-16260

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.