# CVE-2018-7282: SQL injection in n/a

> An attacker can exploit a SQL injection vulnerability in the login request to read sensitive data from the TITool PrintMonitor database.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4p5m-mv2p-frm5

## What is CVE-2018-7282?

CVE-2018-7282 is a critical SQL injection vulnerability in n/a, published on 6 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The username parameter of the TITool PrintMonitor solution during the login request is vulnerable to and/or time-based blind SQLi.

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

## Which versions are affected by CVE-2018-7282?

It affects 1 product.


Products: Titool Printmonitor.

## How do I fix CVE-2018-7282?

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

## Is CVE-2018-7282 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-7282 exists.

Public exploit code:

- TITool PrintMonitor - Blind SQL Injection (nuclei): http/cves/2018/CVE-2018-7282.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7282 and fix it if it is affected.

What it is: CVE-2018-7282 is a critical SQL injection vulnerability in n/a, published on 6 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-7282 exists.

Affected product: n/a. 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-2018-7282/ (Markdown: https://insights.sbomify.com/CVE-2018-7282/index.md)
```

## Sources

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

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