Quick answers
- Is CVE-2026-48239 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48239 being exploited in the wild.
- How severe is CVE-2026-48239?
- High severity, with a CVSS score of 7.1, published 21 May 2026.
- Which products and versions are affected?
- Open ISES Tickets before 3.44.2.
- Is there a fix for CVE-2026-48239?
- A patch was published on 2026-04-01: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48239 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48239?
- Check whether you run Open ISES Tickets 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
A SQL injection vulnerability exists in Open ISES Tickets versions prior to 3.44.2 within the 'ajax/reports.php' component. The root cause is the direct concatenation of the 'tick_id' POST parameter into the WHERE clause of SQL SELECT statements used for incident summary reports. An authenticated attacker with network access can exploit this by sending specially crafted POST requests to manipulate the underlying database queries. Successful exploitation allows for unauthorized data retrieval (including sensitive incident details), data modification, or data destruction. The issue is resolved in version 3.44.2 by implementing proper input sanitization using 'intval()'.
Affected products
- Open ISES Tickets before 3.44.2
Timeline
- 2026-04-01: patched: Fix committed to repository
- 2026-04-02: advisory: Release v3.44.2 published
- 2026-05-21: disclosed: CVE published and NVD record created