Open ISES Tickets SQL Injection Vulnerability (CVE-2026-48235)
Open ISES Tickets versions before 3.44.2 are vulnerable to SQL injection (CVE-2026-48235) due to unsanitized GPS data, allowing attackers to manipulate responder data by compromising the GPS tracker endpoint.
CVE search metadata
CVE search record: CVE-2026-48235. Severity: high. CVSS: 8.2. KEV: no. Product: Open ISES Tickets < 3.44.2. Brief: Open ISES Tickets SQL Injection Vulnerability (CVE-2026-48235). Brief link: https://feed.craftedsignal.io/briefs/2026-05-21-open-ises-tickets-sql-injection/
Triage facts
Revision 2- Applicability
- Open ISES Tickets < 3.44.2
- Evidence
- Unknown
- Severity
- High
- Sources
- 1 public source
- Freshness
- Revision 2May 21, 18:19 UTC
- Detection
- 2 rules
- Vulnerabilities
- 1 CVE
Revision history 1 entry · Revision 2
- Revision 2
Repaired a legacy canonical identity collision
Changed: slug
Open ISES Tickets versions before 3.44.2 are susceptible to a SQL injection vulnerability (CVE-2026-48235) stemming from the processing of GPS data. The vulnerability lies in incs/remotes.inc.php, where latitude, longitude, callsign, mph, altitude, and timestamp values extracted from external GPS tracking services (InstaMapper and Google Latitude) are directly concatenated into SQL queries. This lack of sanitization creates an opportunity for attackers who can compromise or impersonate the remote GPS tracker endpoint to inject arbitrary SQL commands, potentially leading to unauthorized data modification within the responder location, tracks, and assignment tables. Exploitation could enable malicious actors to manipulate responder deployments and track data.
Attack Chain
- The attacker identifies an Open ISES Tickets instance using InstaMapper or Google Latitude integration.
- The attacker gains control over, or impersonates, the remote GPS tracker endpoint.
- The attacker crafts malicious XML/JSON responses containing SQL injection payloads in the latitude, longitude, callsign, mph, altitude, or timestamp fields.
- The Open ISES Tickets server parses the crafted XML/JSON response from the compromised GPS tracker.
- The server concatenates the unsanitized data into UPDATE or INSERT SQL statements within
incs/remotes.inc.php. - The injected SQL code is executed against the Open ISES Tickets database.
- The attacker manipulates responder location, tracks, and assignment data within the database.
- The attacker achieves their objective, such as diverting responders or falsifying tracking information.
Impact
Successful exploitation of this SQL injection vulnerability (CVE-2026-48235) could allow an attacker to manipulate responder deployments, tracks, and assignments. This could lead to incorrect responder dispatches, delayed response times, or complete disruption of the incident management system. The impact is significant, potentially affecting public safety and emergency response operations that rely on accurate location data.
Recommendation
- Upgrade Open ISES Tickets to version 3.44.2 or later to patch CVE-2026-48235.
- Implement input validation and sanitization on all GPS data received from external sources to prevent SQL injection, focusing on the latitude, longitude, callsign, mph, altitude, and timestamp fields.
- Deploy the Sigma rule
Detect Suspicious GPS Data in Web Requeststo identify potential SQL injection attempts. - Harden the GPS tracker endpoint by implementing strong authentication and authorization controls to prevent unauthorized access and impersonation.
Detection coverage 2
Detect Suspicious GPS Data in Web Requests
highDetects CVE-2026-48235 exploitation - attempts to inject SQL commands via GPS data in web requests to Open ISES Tickets.
Detect SQL Injection Characters in HTTP POST Requests
mediumDetects common SQL injection characters in HTTP POST requests, potentially indicating exploitation attempts.
Detection queries are available on the platform. Get full rules →