Authenticated database compromise via unsanitized message identifiers
Published May 21, 2026 · Updated May 21, 2026
SQL injection in Open ISES Tickets CAD before 3.44.2 allows remote authenticated users to alter database contents through crafted POST requests. message.php concatenates the frm_ticket_id and frm_resp_id POST values directly into SELECT and UPDATE WHERE clauses without sanitization or parameterization. A valid login is required; successful exploitation permits direct database reads, writes, or deletion through changed query semantics.
Summary
What happened
SQL injection in Open ISES Tickets CAD before 3.44.2 allows remote authenticated users to alter database contents through crafted POST requests. message.php concatenates the frm_ticket_id and frm_resp_id POST values directly into SELECT and UPDATE WHERE clauses without sanitization or parameterization. A valid login is required; successful exploitation permits direct database reads, writes, or deletion through changed query semantics.
The record
- CVE
- CVE-2026-48237
- Published
- May 21, 2026
- Updated
- May 21, 2026
- Vendor
- Open ISES
- Product
- Tickets CAD
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2026CVE publishedPublication date reported by the CVE source.
- May 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.44.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo