# CVE-2026-35010: Open ISES Tickets < 3.44.2 Reflected XSS via patient_JF.php ticket_id Parameter

> Authenticated attackers can inject arbitrary JavaScript via the ticket_id parameter in patient_JF.php, leading to script execution in victim browsers.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 May 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-p7vj-52m5-2hp4

## What is CVE-2026-35010?

CVE-2026-35010 is a medium-severity cross-site scripting vulnerability in openises tickets, published on 20 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Open ISES Tickets before 3.44.2 contains a reflected cross-site scripting vulnerability in patient_JF.php that allows authenticated attackers to inject arbitrary JavaScript by passing an unsanitized value through the ticket_id GET parameter directly into a JavaScript variable assignment. Attackers can craft a malicious URL containing a JavaScript payload in the ticket_id parameter that executes in the victim's browser when the URL is visited.

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

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


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

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

## Is CVE-2026-35010 being exploited?

There is no known exploitation of CVE-2026-35010 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-35010 is a medium-severity cross-site scripting vulnerability in openises tickets, published on 20 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-35010 in the wild and no public exploit code.

Affected product: openises tickets. 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-35010/ (Markdown: https://insights.sbomify.com/CVE-2026-35010/index.md)
```

## Sources

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

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