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

> Unauthenticated attackers can exploit SQL injection in CMG Suite to extract database information and execute arbitrary scripts.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 25 Apr 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m7gh-xg3x-jmw6

## What is CVE-2018-18286?

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

### Official description

SQL injection vulnerabilities in CMG Suite 8.4 SP2 and earlier, could allow an unauthenticated attacker to conduct an SQL injection attack due to insufficient input validation for the changepwd interface. A successful exploit could allow an attacker to extract sensitive information from the database and execute arbitrary scripts.

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

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

It affects 1 product.


Products: Mitel Cmg Suite.

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

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

## Is CVE-2018-18286 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18285](https://insights.sbomify.com/CVE-2018-18285/): SQL injection in n/a (critical 9.8)
- [CVE-2018-19275](https://insights.sbomify.com/CVE-2018-19275/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18286 is a critical SQL injection vulnerability in n/a, published on 25 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-18286 in the wild and no public exploit code.

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-18286/ (Markdown: https://insights.sbomify.com/CVE-2018-18286/index.md)
```

## Sources

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

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