Quick answers
- Is CVE-2026-92263 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92263 being exploited in the wild.
- How severe is CVE-2026-92263?
- High severity, with a CVSS score of 7.2, published 16 October 2026.
- Which products and versions are affected?
- CodeWithCJ SparkyFitness before 1.6.0.
- Is there a fix for CVE-2026-92263?
- Yes: fixed in 1.6.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92263 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-92263?
- Check whether you run CodeWithCJ SparkyFitness at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.6.0
Technical details
The api/admin/backup/restore endpoint interpolates an uploaded filename directly into a shell command without proper escaping. An authenticated global administrator can exploit this command injection by uploading a restore archive with shell metacharacters in the filename. The fix in version 1.6.0 replaces shell-based execution with argv-based execFile to prevent metacharacter interpretation.
Affected products
- CodeWithCJ SparkyFitness before 1.6.0
Timeline
- 2026-07-09: patched
- 2026-10-16: disclosed