# CVE-2026-48238: Open ISES Tickets < 3.44.2 SQL Injection via ajax/mobile_main.php id Parameter

> Authenticated attackers can exploit SQL injection in Open ISES Tickets to read, modify, or destroy database contents via the id parameter.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-8wx2-2gr7-3c4q

## What is CVE-2026-48238?

CVE-2026-48238 is a high-severity SQL injection vulnerability in Open ISES Tickets, published on 21 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Open ISES Tickets before 3.44.2 contains a SQL injection vulnerability in ajax/mobile_main.php where the id GET parameter is concatenated into the WHERE clause of a SELECT statement used as a ticket-existence sanity check without sanitization. Authenticated attackers can craft requests that alter query semantics to read, modify, or destroy database contents.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-48238?


## How do I fix CVE-2026-48238?

No fix has been published for CVE-2026-48238 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-48238 being exploited?

There is no known exploitation of CVE-2026-48238 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48238 and fix it if it is affected.

What it is: CVE-2026-48238 is a high-severity SQL injection vulnerability in Open ISES Tickets, published on 21 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48238 in the wild and no public exploit code.

Affected product: Open ISES Tickets. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48238/ (Markdown: https://insights.sbomify.com/CVE-2026-48238/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48238
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48238
- OSV: https://osv.dev/vulnerability/CVE-2026-48238

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48238/
Summaries are generated and may contain mistakes; the official description above is the record.