CVE-2024-32963 Vulnerability Analysis & Exploit Details

CVE-2024-32963
Vulnerability Scoring

4.2
/10
Medium Risk

The vulnerability CVE-2024-32963 could compromise system integrity but typically requires user interaction to be exploited.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2024-32963 Details

Status: Analyzed

Last updated: 🕡 26 Aug 2025, 18:52 UTC
Originally published on: 🕖 01 May 2024, 07:15 UTC

Time between publication and last update: 482 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

CVE-2024-32963 Vulnerability Summary

CVE-2024-32963: Navidrome is an open source web-based music collection server and streamer. In affected versions of Navidrome are subject to a parameter tampering vulnerability where an attacker has the ability to manipulate parameter values in the HTTP requests. The attacker is able to change the parameter values in the body and successfully impersonate another user. In this case, the attacker created a playlist, added song, posted arbitrary comment, set the playlist to be public, and put the admin as the owner of the playlist. The attacker must be able to intercept http traffic for this attack. Each known user is impacted. An attacker can obtain the ownerId from shared playlist information, meaning every user who has shared a playlist is also impacted, as they can be impersonated. This issue has been addressed in version 0.52.0 and users are advised to upgrade. There are no known workarounds for this vulnerability.

Assessing the Risk of CVE-2024-32963

Access Complexity Graph

The exploitability of CVE-2024-32963 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2024-32963

This vulnerability, CVE-2024-32963, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2024-32963, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2024-32963, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2024-32963 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2024-32963 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2024-32963 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.043% (probability of exploit)

EPSS Percentile: 12.0% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 88.0% of others.

CVE-2024-32963 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:a:navidrome:navidrome:-:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:-:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.7.2:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.7.3:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.7.3:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.8.2:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.8.3:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.8.3:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.8.4:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.8.4:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.9.2:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.9.3:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.9.3:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.11.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.11.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.11.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.12.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.12.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.13.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.13.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.14.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.14.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.14.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.14.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.14.2:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.14.2:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.14.3:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.14.3:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.14.4:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.14.4:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.14.5:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.14.5:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.15.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.15.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.16.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.16.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.16.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.16.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.17.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.17.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.18.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.18.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.19.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.19.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.20.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.20.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.21.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.21.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.22.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.22.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.23.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.23.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.23.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.23.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.24.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.24.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.25.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.25.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.26.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.26.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.26.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.26.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.27.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.27.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.28.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.28.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.29.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.29.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.30.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.30.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.30.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.30.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.31.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.31.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.32.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.32.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.33.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.33.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.34.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.34.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.34.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.34.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.35.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.35.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.35.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.35.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.36.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.36.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.36.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.36.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.37.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.37.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.38.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.38.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.39.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.39.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.40.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.40.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.41.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.41.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.41.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.41.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.42.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.42.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.42.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.42.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.43.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.43.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.44.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.44.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.44.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.44.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.45.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.45.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.45.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.45.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.46.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.46.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.47.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.47.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.47.5:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.47.5:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.48.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.48.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.49.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.49.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.49.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.49.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.49.2:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.49.2:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.49.3:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.49.3:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.50.0:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.50.0:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.50.1:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.50.1:*:*:*:*:*:*:*
  • cpe:2.3:a:navidrome:navidrome:0.50.2:*:*:*:*:*:*:*
    cpe:2.3:a:navidrome:navidrome:0.50.2:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-32963: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-10273 – A vulnerability was identified in erjinzhi 10OA 1.0. Affected by this vulnerability is an unknown functionality of the file /view/file.aspx. Such m...
  • CVE-2025-10272 – A vulnerability was determined in erjinzhi 10OA 1.0. Affected is an unknown function of the file /trial/mvc/catalogue. This manipulation of the arg...
  • CVE-2025-10271 – A vulnerability was found in erjinzhi 10OA 1.0. This impacts an unknown function of the file /trial/mvc/finder. The manipulation of the argument Na...
  • CVE-2025-36222 – IBM Fusion 2.2.0 through 2.10.1, IBM Fusion HCI 2.2.0 through 2.10.0, and IBM Fusion HCI for watsonx 2.8.2 through 2.10.0 uses insecure default con...
  • CVE-2025-10127 – Daikin Security Gateway is vulnerable to an authorization bypass through a user-controlled key vulnerability that could allow an attacker to bypa...