BrightSign players running BrightSign OS series 4 prior to v8.5.53.1 or series 5 prior to v9.0.166 use a default password that is guessable with knowledge of the device information. The latest release fixes this issue for new installations; users of old installations are encourag...
Vendor
brightsign vulnerabilities
6 published CVES affecting brightsign, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 1
- High
- 3
- Medium
- 2
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Products
- 4k242 firmware 3
- BrightSign OS series 4 players 2
- BrightSign OS series 5 players 2
- BrightSign Digital Signage Diagnostic Web Server 1
Latest brightsign CVEs
Newest publication first
-
HighCVSS 8.6 EPSS 0.15%
-
CVE-2020-36884 BrightSign Digital Signage Diagnostic Web Server 8.2.26 Unauthenticated SSRF
PublishedMediumCVSS 6.9 EPSS 1.2%BrightSign Digital Signage Diagnostic Web Server 8.2.26 and less contains an unauthenticated server-side request forgery vulnerability in the 'url' GET parameter of the Download Speed Test service. Attackers can specify external domains to bypass firewalls and perform network enu...
-
HighCVSS 8.5 EPSS 0.19%
BrightSign players running BrightSign OS series 4 prior to v8.5.53.1 or series 5 prior to v9.0.166 contain an execution with unnecessary privileges vulnerability, allowing for privilege escalation on the device once code execution has been obtained.
-
MediumCVSS 6.1 EPSS 2.1%
The BrightSign Digital Signage (4k242) device (Firmware 6.2.63 and below) has XSS via the REF parameter to /network_diagnostics.html or /storage_info.html.
-
HighCVSS 7.5 EPSS 5.8%
The BrightSign Digital Signage (4k242) device (Firmware 6.2.63 and below) allows renaming and modifying files via /tools.html.
-
CriticalCVSS 9.8 EPSS 11.9%
The BrightSign Digital Signage (4k242) device (Firmware 6.2.63 and below) has directory traversal via the /storage.html rp parameter, allowing an attacker to read or write to files.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.