Patient-form disclosure via unbound request identifiers
Published Feb 25, 2026 · Updated Feb 25, 2026
Authorization bypass in OpenEMR before 8.0.0 allows remote authenticated users to view other patients’ LBF encounter forms. The printable.php endpoint uses request-supplied formid and visitid values to query and render a form without binding them to the session patient and encounter. LBF access and a guessed or enumerated valid form and visit ID are required, and successful exploitation discloses another patient’s protected health information.
Summary
What happened
Authorization bypass in OpenEMR before 8.0.0 allows remote authenticated users to view other patients’ LBF encounter forms. The printable.php endpoint uses request-supplied formid and visitid values to query and render a form without binding them to the session patient and encounter. LBF access and a guessed or enumerated valid form and visit ID are required, and successful exploitation discloses another patient’s protected health information.
The record
- CVE
- CVE-2026-25930
- Published
- Feb 25, 2026
- Updated
- Feb 25, 2026
- Vendor
- OpenEMR Foundation
- Product
- OpenEMR
- Classifications
- CWE-639, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 25, 2026CVE publishedPublication date reported by the CVE source.
- Feb 25, 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=< 8.0.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
- GHSA-h3xx-8cp7-hf7m printable LBF 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