CVE-2026-48237: Open ISES Tickets < 3.44.2 SQL Injection via message.php frm_ticket_id and frm_resp_id Parameters
Open ISES Tickets before 3.44.2 contains a SQL injection vulnerability in message.php where the frm_ticket_id and frm_resp_id POST parameters are concatenated into WHERE clauses of SELECT/UPDATE statements without sanitization. Authenticated attackers can craft requests that alter query semantics to read, modify, or destroy database contents.
Security readout for executives and security teams
Plain-English summary
Authenticated users can manipulate database queries in Open ISES Tickets versions before 3.44.2. Successful abuse could expose ticket data, alter records, or damage database contents. Because exploitation is remote, low-complexity, and requires no user interaction, affected deployments should upgrade promptly.
Executive priority
Prioritize remediation in the current patch cycle, escalating internet-accessible or broadly accessible deployments. Immediate attention is justified where sensitive ticket information is stored or many low-privilege accounts exist. Investigate suspicious activity if logging indicates anomalous message.php requests or unexplained database changes.
Technical view
CVE-2026-48237 is a CWE-89 SQL injection in message.php. The frm_ticket_id and frm_resp_id POST parameters are concatenated into SELECT and UPDATE WHERE clauses without sanitization. CVSS 4.0 rates it 7.1: network-accessible, low complexity, low privileges required, no user interaction, with high confidentiality impact.
Likely exposure
Exposure is likely where Open ISES Tickets earlier than 3.44.2 is reachable by authenticated, low-privilege users. Public internet exposure increases opportunity, but internal deployments remain vulnerable to compromised or malicious accounts. The supplied affected-version metadata is inconsistent, so inventory confirmation is important.
Exploitation context
The source bundle does not identify CISA KEV inclusion or provide evidence of active exploitation. The flaw nevertheless has practical risk because an authenticated attacker can reach it remotely with low complexity and without victim interaction. No exploit procedure is provided here.
Researcher notes
The vendor commit and 3.44.2 release are the strongest remediation evidence supplied. The bundle describes vulnerable versions as earlier than 3.44.2, but its structured affected entry lists version “0” with a default unaffected status. Treat version enumeration cautiously and reconcile inventory against vendor guidance.
Mitigation direction
Upgrade Open ISES Tickets to version 3.44.2 or later using vendor guidance.
Restrict message.php access to trusted users and networks until upgrading.
Review and reduce account privileges, especially for unnecessary or dormant users.
Preserve verified database backups before remediation and confirm restoration readiness.
Monitor vendor and CVE guidance for revised affected-version information.
Validation and detection
Inventory Open ISES Tickets deployments and confirm their exact installed versions.
Verify production systems run version 3.44.2 or later.
Confirm the vendor patch protects both identified POST parameters.
Review application logs for unusual POST requests to message.php.
Examine database audit records for unexpected ticket queries, changes, or deletions.
Run authorized regression testing without destructive payloads after upgrading.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.