Incident Score: Analysis & Impact (OPE1782476713)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of Open Medical's Vulnerability and lateral movement inside company's environment.
- Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
- How Rankiteo’s incident engine converts technical details into a normalized incident score.
- How this cyber incident impacts Open Medical Rankiteo cyber scoring and cyber rating.
- Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.
Full Incident Analysis Transcript
In this Rankiteo incident briefing, we review the Open Medical breach identified under incident ID OPE1782476713.
The analysis begins with a detailed overview of Open Medical's information like the linkedin page: https://www.linkedin.com/company/openmedical, the number of followers: 10873, the industry type: Hospitals and Health Care and the number of employees: 52 employees
After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 760 and after the incident was 749 with a difference of -11 which is could be a good indicator of the severity and impact of the incident.
In the next step of the video, we will analyze in more details the incident and the impact it had on Open Medical and their customers.
On 18 May 2026, OHIF (Open Health Imaging Foundation) disclosed Server-Side Request Forgery (SSRF) issues under the banner "High-Severity SSRF Vulnerability in OHIF Viewers DICOM Exposes Clinician Tokens".
A high-severity Server-Side Request Forgery (SSRF) vulnerability (CVE-2026-12473) has been discovered in OHIF (Open Health Imaging Foundation) Viewers DICOM, a widely used medical imaging framework.
The disruption is felt across the environment, affecting OHIF DICOM Web Viewer Framework (versions prior to 3.12.0), and exposing OIDC Bearer tokens (clinician authentication tokens).
In response, moved swiftly to contain the threat with measures like Patch released (version 3.12.2), and began remediation that includes Upgrade to OHIF Viewers version 3.12.2 or later; review additional mitigation steps in CISA security advisory.
The case underscores how Resolved (patch released), and recommending next steps like Upgrade to patched version (3.12.2 or later); implement input validation for URL parameters; review CISA advisory for additional mitigations, with advisories going out to stakeholders covering Organizations using OHIF urged to upgrade and review CISA advisory.
Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.
The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.
MITRE ATT&CK® Correlation Analysis
Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Phishing: Spearphishing Link (T1566.002) with high confidence (90%), with evidence including tricking them into clicking a malicious link, and attack vector such as Malicious link (phishing). Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1528) with high confidence (95%), with evidence including steal an authenticated clinician’s OIDC Bearer token, and data compromised such as OIDC Bearer tokens and Unsecured Credentials: Network Device Authentication (T1552.008) with moderate to high confidence (70%), supported by evidence indicating global authentication service in OHIF injects the clinician’s token into the request. Under the Execution tactic, the analysis identified Exploitation for Client Execution (T1203) with moderate to high confidence (80%), supported by evidence indicating server-Side Request Forgery (SSRF) vulnerability (CVE-2026-12473). Under the Lateral Movement tactic, the analysis identified Exploitation of Remote Services (T1210) with moderate to high confidence (70%), with evidence including potential unauthorized access to medical imaging systems, and dICOMWebProxy and DICOMJSON fetch arbitrary URL parameters. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), with evidence including sending it to an attacker-controlled server, and data exfiltration such as Possible if exploited. Under the Defense Evasion tactic, the analysis identified Modify Authentication Process (T1556) with moderate to high confidence (70%), supported by evidence indicating injects the clinician’s token into the request, potentially sending it to an attacker. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Open Medical Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/openmedical/incident/OPE1782476713
- Open Medical CyberSecurity Rating page: https://www.rankiteo.com/company/openmedical
- Open Medical Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/ope1782476713-open-health-imaging-foundation-vulnerability-may-2026/
- Open Medical CyberSecurity Score History: https://www.rankiteo.com/company/openmedical/history
- Open Medical CyberSecurity Incident Source: https://www.hipaajournal.com/high-severity-vulnerability-identified-in-ohif-viewers-dicom/
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf