# CVE-2026-25743: OpenEMR has Stored XSS in Questionnaire answers

> Authenticated attackers with Forms administration role can inject malicious JavaScript into questionnaire answers, leading to stored XSS execution for other users.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Feb 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-3xx2-qf6g-6p28

## What is CVE-2026-25743?

CVE-2026-25743 is a high-severity cross-site scripting vulnerability in Open-Emr Openemr, published on 25 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0, users with the "Forms administration" role can fill questionnaires ("forms") in patient encounters. The answers to the forms are displayed on the encounter page and in the visit history for the users with the same role. There exists a stored cross-site scripting (XSS) vulnerability in the function to display the form answers, allowing any authenticated attacker with the specific role to insert arbitrary JavaScript into the system by entering malicious payloads to the form answers. The JavaScript code is later executed by any user with the form role when viewing the form answers in the patient encounter pages or visit history. Version 8.0.0 fixes the issue.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-25743?

It affects 1 product.


Products: Open-Emr Openemr.

## How do I fix CVE-2026-25743?

No fix has been published for CVE-2026-25743 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-25743 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25743 exists.

## Other vulnerabilities in Open-Emr Openemr

- [CVE-2026-24898](https://insights.sbomify.com/CVE-2026-24898/): OpenEMR has an Unauthenticated MedEx Token Disclosure (critical 10.0)
- [CVE-2026-24849](https://insights.sbomify.com/CVE-2026-24849/): OpenEMR Arbitrary File Read Vulnerability (critical 10.0)
- [CVE-2026-24908](https://insights.sbomify.com/CVE-2026-24908/): OpenEMR has SQL Injection in Patient API Sort Parameter (critical 10.0)
- [CVE-2022-2734](https://insights.sbomify.com/CVE-2022-2734/): Improper Restriction of Rendered UI Layers or Frames in openemr/openemr (critical 10.0)
- [CVE-2024-22611](https://insights.sbomify.com/CVE-2024-22611/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25743 and fix it if it is affected.

What it is: CVE-2026-25743 is a high-severity cross-site scripting vulnerability in Open-Emr Openemr, published on 25 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25743 exists.

Affected product: Open-Emr Openemr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25743/ (Markdown: https://insights.sbomify.com/CVE-2026-25743/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25743
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25743
- OSV: https://osv.dev/vulnerability/CVE-2026-25743

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25743/
Summaries are generated and may contain mistakes; the official description above is the record.