Comparison Overview
Singing River Health System
Singing River Health System
3109 Bienville Blvd, Ocean Springs, 39564, US
Last Update: 20/05/2026
Singing River offers award-winning, comprehensive care for every age and stage. As one of South Mississippi's largest employers and proudly recognized on the Forbes list of America’s Best-In-State Employers, we are committed to the highest quality standards and attracti...
Philips
Amstelplein 2, Amsterdam, 1096 BC, NL
Last Update: 14/08/2026
Over the past decade we have transformed into a focused leader in health technology. At Philips, our purpose is to improve people’s health and well-being through meaningful innovation. We aim to improve 2.5 billion lives per year by 2030, including 400 million in under...
Compliance Ranges Comparison
Singing River Health System
Philips
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Singing River Health System in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Philips has 191.26% more incidents than the average of all companies with at least one recorded incident.
Incident History - Singing River Health System (X = Date, Y = Severity)
Singing River Health System cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Philips (X = Date, Y = Severity)
Philips cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Singing River Health System
Philips
FAQ
Latest Global CVEs
A vulnerability has been found in SourceCodester Simple Online Food Ordering System 1.0. This affects an unknown function of the file /admin/ajax.php?action=login2. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
A flaw was found in the ipa_getkeytab module of the community.general Ansible collection. The module's bind_pw parameter, used to supply the LDAP simple-bind password when retrieving a Kerberos keytab, is not declared with no_log, unlike the sibling password parameter in the same module. As a consequence, the supplied IPA/LDAP bind password is recorded in cleartext in the managed host's system journal/syslog (the module's "Invoked with" record), is included in the module's return values and verbose (-v) output, and is displayed in Automation Controller / AWX job output. The password is additionally passed on the command line to the ipa-getkeytab helper (as --bindpw <value>), exposing it in the process list to local users while the command runs. An attacker able to read these logs, job output, or the process table can obtain the directory bind credential, potentially compromising the accounts and objects that credential can access.
The device metadata import interface /device/instance/{productId}/property-metadata/import of jetlinks community 2.11 is vulnerable to Server-side request forgery (SSRF).
disconf (Distributed Configuration Management Platform) 2.6.36 is vulnerable to Incorrect Access Control. The config-fetching APIs /api/config/item, /api/config/file, /api/config/list and /api/config/simple/list are exposed without authentication. The LoginInterceptor explicitly whitelists these four paths, so any anonymous attacker can read every configuration item and configuration file managed by the config center.
Funiture 1.0.0 is vulnerable to SQL Injection in the backend tool interfaces /sys/tool/select.json and /sys/tool/update.json.