PatchSiren cyber security CVE debrief
CVE-2025-54756 BrightSign CVE debrief
BrightSign reported a default-password weakness in BrightSign OS series 4 players before v8.5.53.1 and series 5 players before v9.0.166. CISA rates the issue 8.4 HIGH. BrightSign says the fixed releases are available, and older installations should have all default passwords changed.
- Vendor
- BrightSign
- Product
- Unknown
- CVSS
- HIGH 8.4
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2025-05-06
- Original CVE updated
- 2026-01-29
- Advisory published
- 2025-05-06
- Advisory updated
- 2026-01-29
Who should care
Administrators and fleet operators managing BrightSign digital-signage players, especially environments running BrightSign OS series 4 or 5 versions below the fixed releases. Security teams responsible for credential hygiene on embedded or kiosk-style devices should also review affected deployments.
Technical summary
According to the CISA CSAF advisory, 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 can be guessed with knowledge of device information. The advisory states the latest release fixes the issue for new installations, while older installations should have all default passwords changed. The supplied CVSS v3.1 vector is AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, with a score of 8.4 (HIGH).
Defensive priority
High
Recommended defensive actions
- Upgrade BrightSign OS series 4 players to v8.5.53.1 or later.
- Upgrade BrightSign OS series 5 players to v9.0.166 or later.
- Change all default passwords on existing installations, not just new deployments.
- Disable the local DWS feature if it is not required, per BrightSign guidance.
- Disable SSH/telnet when not in use.
- Limit physical access to players and disable SD/USB ports if they are not needed.
Evidence notes
The supplied CISA CSAF advisory (ICSA-25-126-03) identifies the affected products, the fixed versions, and the recommendation to change default passwords on older installations. The CVE was published on 2025-05-06 and later updated on 2026-01-29 with Update A that added CVE-2025-54756 to the advisory metadata. No KEV listing is present in the supplied data.
Sources and references
Verified primary and authoritative sources
-
CVE-2025-54756 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2025-54756
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2025-54756 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2025-54756
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source item URL
Unverified legacy reference
URL: https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/OT/white/2025/icsa-25-126-03.json
cisa_csaf
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/news-events/ics-advisories/icsa-25-126-03
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/uscert/ics/alerts/ICS-ALERT-10-301-01
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/resources-tools/resources/ics-recommended-practices
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/sites/default/files/publications/Cybersecurity_Best_Practices_for_Industrial_Control_Systems.pdf
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/topics/industrial-control-systems
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/news-events/ics-alerts/ics-alert-10-301-01
Reference
-
Source reference
Unverified legacy reference
URL: https://www.cisa.gov/sites/default/files/recommended_practices/NCCIC_ICS-CERT_Defense_in_Depth_2016_S508C.pdf
Reference
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.