# CVE-2025-48949: Navidrome allows SQL Injection via role parameter

> Attackers can inject SQL via the role parameter in Navidrome to access the database and compromise user data.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 May 2025
- **Updated:** 30 May 2025
- **Also known as:** GHSA-5wgp-vjxm-3x2r, GO-2025-3734

## What is CVE-2025-48949?

CVE-2025-48949 is a high-severity SQL injection vulnerability in navidrome, published on 30 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Navidrome is an open source web-based music collection server and streamer. Versions 0.55.0 through 0.55.2 have a vulnerability due to improper input validation on the `role` parameter within the API endpoint `/api/artist`. Attackers can exploit this flaw to inject arbitrary SQL queries, potentially gaining unauthorized access to the backend database and compromising sensitive user information. Version 0.56.0 contains a patch for the issue.

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

## Which versions are affected by CVE-2025-48949?

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 | From 0.55.0 | 0.56.0 |
| `github.com/navidrome/navidrome` | Go | From 0.55.0 | 0.56.0 |
| `github.com/navidrome/navidrome` | Go | From 0.55.0 | 0.56.0 |

Products: Navidrome Navidrome.

## How do I fix CVE-2025-48949?

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

## Is CVE-2025-48949 being exploited?

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

## Other vulnerabilities in navidrome

- [CVE-2024-47062](https://insights.sbomify.com/CVE-2024-47062/): Multiple SQL Injections and ORM Leak in navidrome (critical 9.4)
- [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-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-2025-48949 and fix it if it is affected.

What it is: CVE-2025-48949 is a high-severity SQL injection vulnerability in navidrome, published on 30 May 2025. 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-2025-48949 exists.

Affected packages and fixed versions:
- github.com/navidrome/navidrome (Go): affected from 0.55.0; fixed in 0.56.0
- github.com/navidrome/navidrome (Go): affected from 0.55.0; fixed in 0.56.0
- github.com/navidrome/navidrome (Go): affected from 0.55.0; fixed in 0.56.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-2025-48949/ (Markdown: https://insights.sbomify.com/CVE-2025-48949/index.md)
```

## Sources

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

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