# CVE-2024-47062: Multiple SQL Injections and ORM Leak in navidrome

> Attackers can inject SQL or leak data via URL parameters to dump the database and brute-force passwords in Navidrome.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Sep 2024
- **Updated:** 20 Sep 2024
- **Also known as:** GHSA-58vj-cv5w-v4v6, GO-2024-3153

## What is CVE-2024-47062?

CVE-2024-47062 is a critical SQL injection vulnerability in navidrome, published on 20 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Navidrome is an open source web-based music collection server and streamer. Navidrome automatically adds parameters in the URL to SQL queries. This can be exploited to access information by adding parameters like `password=...` in the URL (ORM Leak). Furthermore, the names of the parameters are not properly escaped, leading to SQL Injections. Finally, the username is used in a `LIKE` statement, allowing people to log in with `%` instead of their username. When adding parameters to the URL, they are automatically included in an SQL `LIKE` statement (depending on the parameter's name). This allows attackers to potentially retrieve arbitrary information. For example, attackers can use the following request to test whether some encrypted passwords start with `AAA`. This results in an SQL query like `password LIKE 'AAA%'`, allowing attackers to slowly brute-force passwords. When adding parameters to the URL, they are automatically added to an SQL query. The names of the parameters are not properly escaped. This behavior can be used to inject arbitrary SQL code (SQL Injection). These vulnerabilities can be used to leak information and dump the contents of the database and have been addressed in release version 0.53.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.

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

## Which versions are affected by CVE-2024-47062?

3 open source packages ship an affected version, including github.com/navidrome/navidrome. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/navidrome/navidrome` | Go | All versions | 0.53.0 |
| `github.com/navidrome/navidrome` | Go | All versions | 0.53.0 |
| `github.com/navidrome/navidrome` | Go | All versions | 0.53.0 |

Products: Navidrome Navidrome.

## How do I fix CVE-2024-47062?

Upgrade github.com/navidrome/navidrome to 0.53.0 or later.

## Is CVE-2024-47062 being exploited?

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

Public exploit code:

- CVE-2024-47062 PoC (github_poc): https://github.com/saisathvik1/CVE-2024-47062
- Navidrome < 0.53.0 - Authenticated SQL Injection (nuclei): http/cves/2024/CVE-2024-47062.yaml

## Other vulnerabilities in navidrome

- [CVE-2026-25579](https://insights.sbomify.com/CVE-2026-25579/): Navidrome affected by Denial of Service and disk exhaustion via oversized `size` parameter in `/rest/getCoverArt` and `/share/img/<token>` endpoints (critical 9.2)
- [CVE-2024-41259](https://insights.sbomify.com/CVE-2024-41259/): Navidrome uses MD5 hashing algorithm (critical 9.1)
- [CVE-2025-48949](https://insights.sbomify.com/CVE-2025-48949/): Navidrome allows SQL Injection via role parameter (high 8.9)
- [CVE-2023-51442](https://insights.sbomify.com/CVE-2023-51442/): Authentication bypass vulnerability in navidrome's subsonic endpoint (high 8.6)
- [CVE-2025-48948](https://insights.sbomify.com/CVE-2025-48948/): Navidrome Transcoding Permission Bypass Vulnerability Report (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47062 and fix it if it is affected.

What it is: CVE-2024-47062 is a critical SQL injection vulnerability in navidrome, published on 20 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47062 exists.

Affected packages and fixed versions:
- github.com/navidrome/navidrome (Go): affected all versions; fixed in 0.53.0
- github.com/navidrome/navidrome (Go): affected all versions; fixed in 0.53.0
- github.com/navidrome/navidrome (Go): affected all versions; fixed in 0.53.0

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

## Sources

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

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