CVE-2026-48239
SQL Injection in Open ISES Tickets
Publication date: 2026-05-21
Last updated on: 2026-05-21
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-48239 is a SQL injection vulnerability found in Open ISES Tickets versions before 3.44.2, specifically in the ajax/reports.php file.
The vulnerability occurs because the tick_id POST parameter is directly concatenated into the WHERE clause of SQL SELECT statements without proper sanitization or neutralization of special characters.
This allows authenticated attackers to craft malicious requests that alter the intended SQL query behavior.
As a result, attackers can manipulate the database queries to read, modify, or delete database contents.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to sensitive data stored in the database.
Attackers can modify or delete data, which could lead to data loss, corruption, or disruption of services.
Because the attacker must be authenticated, the risk is limited to users with some level of access, but the damage can still be significant.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Open ISES Tickets to version 3.44.2 or later, where the issue has been fixed.
The vulnerability is caused by improper sanitization of the tick_id POST parameter in ajax/reports.php, so applying the official patch or update will neutralize this risk.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows authenticated attackers to read, modify, or delete database contents by exploiting a SQL injection flaw. Such unauthorized access and manipulation of data can lead to breaches of sensitive information.
This kind of data compromise can negatively impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data against unauthorized access and alteration.