Stored XSS in Imaster Patient Record Management System edit_patient.php (firstname)
Imaster's Patient Record Management System is vulnerable to stored cross-site scripting (XSS) in the administrative endpoint /projects/hospital/admin/edit_patient.php. An attacker can inject malicious JavaScript into the firstname parameter such that the payload is stored server-side and subsequently rendered without proper output encoding. The stored script executes in a victim’s browser whenever the patient list is viewed, enabling arbitrary JavaScript execution in the context of the application.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
/projects/hospital/admin/edit_patient.php to trusted users/networks; add strict server-side validation/sanitization for firstname; ensure output encoding in the patient list view; deploy a restrictive Content Security Policy (CSP) to reduce script execution impact; and implement WAF rules to detect/block common XSS payloads targeting the affected endpoint.Remediation
Patch, then assume compromise.
firstname (and similar fields), and apply context-appropriate output encoding when rendering patient data in the patient list and related views. Apply a vendor-provided patch/fixed release when available.Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.