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

> SQL injection in the Music Collection component for Joomla allows attackers to manipulate database queries via the id parameter.

- **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:** 28 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gm6r-h85c-pxp8

## What is CVE-2018-17375?

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

### Official description

SQL Injection exists in the Music Collection 3.0.3 component for Joomla! via the id parameter.

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

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

It affects 1 product.


Products: Joomlathat Music Collection.

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

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

## Is CVE-2018-17375 being exploited?

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

Public exploit code:

- Joomla! Component Music Collection 3.0.3 - SQL Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-17375 is a critical SQL injection vulnerability in n/a, published on 28 Sep 2018. 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-17375 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-17375/ (Markdown: https://insights.sbomify.com/CVE-2018-17375/index.md)
```

## Sources

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

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