Session hijacking via unsanitized template filename
Published Apr 25, 2022 · Updated Aug 3, 2024
Stored XSS in OpenEMR before 6.1.0.1 allows remote authenticated users to hijack sessions via crafted template filenames. The document-template manager passes the selected filename to jQuery html() without first applying the project's jsText() escaping function. An authenticated user must store the filename and another user must trigger its rendering, exposing that user's session to script theft.
Summary
What happened
Stored XSS in OpenEMR before 6.1.0.1 allows remote authenticated users to hijack sessions via crafted template filenames. The document-template manager passes the selected filename to jQuery html() without first applying the project's jsText() escaping function. An authenticated user must store the filename and another user must trigger its rendering, exposing that user's session to script theft.
The record
- CVE
- CVE-2022-1458
- Published
- Apr 25, 2022
- Updated
- Aug 3, 2024
- Vendor
- OpenEMR Foundation
- Product
- OpenEMR
- Classifications
- CWE-79, T1539
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 25, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=unspecified <6.1.0.1
What conditions does exploitation require?
What is affected?
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
- huntr.dev CVE-2022-1458 bounty exploit artifactproof of concept · unverified
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