CVE-2025-48949
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNavidrome 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceNavidrome versions 0.55.0-0.55.2 contain a SQL injection vulnerability in the /api/artist endpoint due to improper input validation on the 'role' parameter. Attackers can inject arbitrary SQL queries to access or modify the backend database.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 0.55.0, < 0.56.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine Navidrome installed versionRun 'navidrome --version' from the command line, or check the version displayed in the UI footer, or inspect the Docker container/tag if running containerizedAffected if Version is 0.55.0, 0.55.1, or 0.55.2 (any version >= 0.55.0 and < 0.56.0)
-
Verify API endpoint exposureConfirm the Navidrome server is running and accessible over network. Check firewall rules or reverse proxy configuration that allows access to the /api/artist endpointAffected if The /api/artist endpoint is reachable from untrusted networks or attackers
-
Check audit logs for suspicious artist queriesReview Navidrome logs for entries containing '/api/artist' with unusual 'role' parameter values such as SQL keywords (SELECT, UNION, INSERT) or malformed inputAffected if Any log entries show SQL injection patterns in the role parameter
-
Inspect database query logsEnable and review database query logging (e.g., PostgreSQL/MySQL general query log) for the period when the /api/artist endpoint was accessed. Look for unexpected or malicious SQL patterns in artist-related queriesAffected if Database logs reveal injected SQL commands originating from artist API requests
You are affected if Navidrome version is 0.55.0 through 0.55.2 and the /api/artist endpoint with the 'role' parameter is accessible to attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.56.0
Upgrade to Navidrome version 0.56.0 or later which contains the patch for this SQL injection vulnerability.
0.56.0
- 1. Back up your Navidrome database and configuration files before upgrading
- 2. Stop the Navidrome service
- 3. Upgrade Navidrome to version 0.56.0 or later using your installation method (e.g., package manager, Docker, or binary)
- 4. Verify the upgrade was successful by checking the version
- 5. Restart the Navidrome service
- 6. Test the /api/artist endpoint to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48949 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48949 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data