Stored XSS via unsanitized template upload
Published Aug 19, 2026 · Updated Aug 19, 2026
Stored XSS in patient portal template import in OpenEMR before 8.3.0 allows remote authenticated users to execute script via template upload. POST /portal/import_template.php stores uploaded template content through DocumentTemplateService and later renders template_content in renderEditorHtml() without sanitizing active HTML or JavaScript; the fix replaces the earlier stripos('<script') check with HTMLPurifier on both write and render paths. Reachability requires Forms Administration permissions and another Forms Administration user to open the template in the HTML editor, after which the injected code runs in that user's browser session and can access or alter data available to that session.
Summary
What happened
Stored XSS in patient portal template import in OpenEMR before 8.3.0 allows remote authenticated users to execute script via template upload. POST /portal/import_template.php stores uploaded template content through DocumentTemplateService and later renders template_content in renderEditorHtml() without sanitizing active HTML or JavaScript; the fix replaces the earlier stripos('<script') check with HTMLPurifier on both write and render paths. Reachability requires Forms Administration permissions and another Forms Administration user to open the template in the HTML editor, after which the injected code runs in that user's browser session and can access or alter data available to that session.
The record
- CVE
- CVE-2026-40508
- Published
- Aug 19, 2026
- Updated
- Aug 19, 2026
- Vendor
- OpenEMR Foundation
- Product
- OpenEMR
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record 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=0 <8.3.0
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
- GitHub advisory proof-of-concept stepsproof 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