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

> An attacker can execute arbitrary SQL commands via the hangup variable in the DISA module, potentially accessing or modifying database contents.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j9pq-6pwh-6xx6

## What is CVE-2018-15892?

CVE-2018-15892 is a medium-severity SQL injection vulnerability in n/a, published on 20 Jun 2019. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

FreePBX 13 and 14 has SQL Injection in the DISA module via the hangup variable on the /admin/config.php?display=disa&view=form page.

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

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

It affects 1 product.


Products: Freepbx Disa.

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

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

## Is CVE-2018-15892 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-15892 is a medium-severity SQL injection vulnerability in n/a, published on 20 Jun 2019. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-15892 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-15892/ (Markdown: https://insights.sbomify.com/CVE-2018-15892/index.md)
```

## Sources

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

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