CVE-2025-12699
Cross-Site Scripting in ZOLL ePCR iOS Enables PHI Exposure
Publication date: 2026-02-10
Last updated on: 2026-02-10
Assigner: ICS-CERT
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| zoll | epcr_ios_application | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-538 | The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in the ZOLL ePCR IOS application where unsanitized user input is reflected into a WebView component. Specifically, attacker-controlled strings placed into PCR fields such as run number, incident, call sign, and notes are interpreted as HTML or JavaScript when the app prints or renders that content.
This allows an attacker to inject scripts that can execute within the app's runtime context. In a proof of concept, these injected scripts were able to read local files containing device and user data.
Because these local files include protected health information (PHI) and device telemetry, the vulnerability enables unauthorized access to sensitive data.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker to read local files on your device through the ePCR application, potentially exposing sensitive information.
The exposed data may include protected health information (PHI) and device telemetry, which could lead to privacy violations, data breaches, and unauthorized disclosure of confidential medical information.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know