Quick answers
- Is CVE-2026-86264 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86264 being exploited in the wild.
- How severe is CVE-2026-86264?
- Medium severity, with a CVSS score of 4.3, published 7 September 2026.
- Which products and versions are affected?
- Sfturing Ssm Pro up to commit 627f426331da8086ce8fff2017d65b1ddef384f8.
- Is there a fix for CVE-2026-86264?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-86264 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-86264?
- Check whether you run Sfturing Ssm Pro 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.
Technical details
This is a stored cross-site scripting (CWE-79) vulnerability in the order creation endpoint (/order) of the OrderController. The vulnerable component accepts user-supplied input for hospitalName, officesName, and doctorName without validation or sanitization, stores it directly in the database, and later renders it in JSP templates using raw EL expressions (${orderRecords.hospitalName}) without HTML encoding. The vulnerability requires user interaction (a victim must view the contaminated appointment record) but no authentication is required to create a malicious appointment. An attacker can execute arbitrary JavaScript in the context of the affected user's session. The project was notified on 2026-07-22 but has not yet provided a patch.
Affected products
- Sfturing ssm_pro up to commit 627f426331da8086ce8fff2017d65b1ddef384f8
Timeline
- 2026-07-22: disclosed: Vulnerability disclosed via GitHub issue #117
- 2026-09-07: advisory: CVE-2026-86264 published