OpenEMR up to 8.0.0.2 POST Parameter json_encode Title cross site scripting

Summaryinfo

A vulnerability identified as problematic has been detected in OpenEMR. This affects the function json_encode of the component POST Parameter Handler. The manipulation of the argument Title leads to cross site scripting. This vulnerability is uniquely identified as CVE-2026-33911. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in OpenEMR. It has been rated as problematic. This issue affects the function json_encode of the component POST Parameter Handler. The manipulation of the argument title with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:

OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0.3, the POST parameter `title` is reflected back in a JSON response built with `json_encode()`. Because the response is served with a `text/html` Content-Type, the browser interprets injected HTML/script tags rather than treating the output as JSON. An authenticated attacker can craft a request that executes arbitrary JavaScript in a victim's session. Version 8.0.0.3 contains a fix.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-33911 since 03/24/2026. The exploitation is known to be easy. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

Upgrading to version 8.0.0.3 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 64e8befa0a49f85dd5e2a85c91f3f8b9e565896f is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Business Process Management Software

Name

• OpenEMR

Version

• 2.8.1
• 2.8.2
• 3.1.0
• 3.2
• 3.2.0
• 4.0.0
• 4.1.0
• 4.1.1
• 5.0.0
• 5.0.0 Patch 1
• 5.0.1
• 5.0.1-6
• 5.0.1-dev
• 5.0.1.1
• 5.0.1.3
• 5.0.1.4
• 5.0.2
• 5.0.2.1
• 5.0.2.4
• 5.0.2.5
• 6.0.0
• 6.0.0-dev
• 6.0.0.0
• 6.0.0.2
• 6.0.0.4
• 6.1.0
• 6.1.0.1
• 7.0.0
• 7.0.0.1
• 7.0.0.2
• 7.0.1
• 7.0.2
• 7.0.2.1
• 7.0.3
• 7.0.3.1
• 7.0.3.4
• 7.0.4
• 7.3.0
• 8.0.0
• 8.0.0.1
• 8.0.0.2

License

• open-source

Website

• Product: https://github.com/openemr/openemr/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion