Stored XSS via unencoded MFA user name
Published Mar 22, 2021 · Updated Apr 30, 2025
Stored XSS in OpenEMR 5.0.2 through 6.0.0 allows remote authenticated users to execute JavaScript through a crafted user name. The MFA registration, TOTP, and U2F pages insert user_full_name into fieldset legends without text encoding, so stored markup reaches another user's browser. Creating the payload requires highly privileged user-administration access, and exploitation requires another user to view an affected MFA page.
Summary
What happened
Stored XSS in OpenEMR 5.0.2 through 6.0.0 allows remote authenticated users to execute JavaScript through a crafted user name. The MFA registration, TOTP, and U2F pages insert user_full_name into fieldset legends without text encoding, so stored markup reaches another user's browser. Creating the payload requires highly privileged user-administration access, and exploitation requires another user to view an affected MFA page.
The record
- CVE
- CVE-2021-25919
- Published
- Mar 22, 2021
- Updated
- Apr 30, 2025
- Vendor
- OpenEMR Foundation
- Product
- OpenEMR
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Mar 22, 2021CVE publishedPublication date reported by the CVE source.
- Apr 30, 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=5.0.2, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.2.4, 6.0.0
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
No public exploit references are available in this record.
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