Stored XSS via unescaped procedure-order patient name
Published May 23, 2025 · Updated May 23, 2025
Stored XSS in OpenEMR before 7.0.3.4 allows remote authenticated users to execute JavaScript through crafted patient names. The procedure-order form assigns an unsanitized patient name to the title array in interface/forms/procedure_order/common.php and renders it without escaping. Patient-creation privileges are required, and the payload runs when another user opens Orders → Procedure Orders, enabling session theft, unauthorized actions, or patient-data disclosure.
Summary
What happened
Stored XSS in OpenEMR before 7.0.3.4 allows remote authenticated users to execute JavaScript through crafted patient names. The procedure-order form assigns an unsanitized patient name to the title array in interface/forms/procedure_order/common.php and renders it without escaping. Patient-creation privileges are required, and the payload runs when another user opens Orders → Procedure Orders, enabling session theft, unauthorized actions, or patient-data disclosure.
The record
- CVE
- CVE-2025-32794
- Published
- May 23, 2025
- Updated
- May 23, 2025
- Vendor
- OpenEMR Foundation
- Product
- OpenEMR
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 23, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 7.0.3.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor advisory proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo