# CVE-2026-4316: Reflected Cross-Site Scripting in software IsMyGym by Zuinq Studio


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-c9jm-46h6-xj8j

## What is CVE-2026-4316?

CVE-2026-4316 is a medium-severity vulnerability in Zuinq Studio IsMyGym, published on 26 Oct 2026. 

### Official description

Reflected Cross-Site Scripting (XSS) in Gym Management Software IsMyGym by Zuinq Studio affecting the reservation endpoint where the 'ret' parameter is reflected in the HTTP response without any proper sanitization. Successfull explotation of this vulnerability could allow an attacker to inject arbitrary JavaScript code executed in the context of the victim’s browser.

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

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


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

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

## Is CVE-2026-4316 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4316 is a medium-severity vulnerability in Zuinq Studio IsMyGym, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-4316 in the wild and no public exploit code.

Affected product: Zuinq Studio IsMyGym. 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-4316/ (Markdown: https://insights.sbomify.com/CVE-2026-4316/index.md)
```

## Sources

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

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