CVE-2026-48239: Open ISES Tickets < 3.44.2 SQL Injection via ajax/reports.php tick_id Parameter
Open ISES Tickets before 3.44.2 contains a SQL injection vulnerability in ajax/reports.php where the tick_id POST parameter is concatenated into the WHERE clause of SELECT statements in the incidents summary report 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
Open ISES Tickets versions before 3.44.2 allow a logged-in attacker to manipulate a database query through a reporting request. Successful abuse could expose sensitive ticket data or change database contents. Because authentication is required, the immediate risk depends on who can access the application and whether accounts are compromised.
Executive priority
Prioritize remediation for externally reachable or sensitive ticketing deployments. Upgrade promptly, then review application and database logs for suspicious authenticated activity. Internal, tightly controlled instances remain important but may be scheduled behind exposed systems after access is verified.
Technical view
CVE-2026-48239 is a CWE-89 SQL injection in ajax/reports.php. The tick_id POST parameter is concatenated into SELECT statement WHERE clauses without sanitization. It is remotely reachable with low complexity, requires low privileges, and needs no user interaction. The supplied CVSS 4.0 score is 7.1.
Likely exposure
Likely exposure is limited to Open ISES Tickets installations earlier than 3.44.2 where authenticated users can access the affected incidents summary reporting endpoint. Internet exposure and weak or compromised accounts increase practical risk. The bundle does not establish how commonly the product or endpoint is deployed.
Exploitation context
The bundle provides no evidence of exploitation in the wild, and the CVE is not identified as being in KEV. Exploitation requires an authenticated account but reportedly can affect database confidentiality and integrity. Treat suspicious authenticated reporting activity as potentially significant.
Researcher notes
The narrative identifies versions before 3.44.2, while the structured affected entry contains version "0" with default status "unaffected." This inconsistency prevents precise version-range interpretation from the bundle alone. The linked 3.44.2 release and patch are the clearest remediation indicators. No exploit-status evidence is supplied.
Mitigation direction
Upgrade Open ISES Tickets to version 3.44.2 or later.
Review the vendor release notes and patch before deployment.
Restrict application access to trusted users until upgrading.
Disable unnecessary accounts and reset credentials suspected of compromise.
Back up the database before remediation and verify backup integrity.
Validation and detection
Inventory all Open ISES Tickets instances and record their exact versions.
Confirm every instance runs version 3.44.2 or later.
Verify the referenced patch is present in deployed application code.
Review access logs for unusual POST requests to ajax/reports.php.
Check database audit records for unexplained reads or modifications.
Confirm authenticated access is limited to expected users.
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.