CVE-2025-50983

readarr · readarr

A high-severity SQL Injection vulnerability, identified as CVE-2025-50983, has been discovered in the readarr application.

Executive summary

A high-severity SQL Injection vulnerability, identified as CVE-2025-50983, has been discovered in the readarr application. This flaw allows a remote attacker to execute arbitrary commands on the application's database by sending a malicious request, potentially leading to unauthorized data access, modification, or deletion, and posing a significant risk to data confidentiality and integrity.

Vulnerability

This is a SQL Injection vulnerability that exists in the sortKey parameter of the /api/v1/wanted/cutoff API endpoint. The application fails to properly sanitize user-supplied input to this parameter before incorporating it into a database query. A remote, unauthenticated attacker can exploit this by crafting a malicious GET request containing specially formatted SQL commands within the sortKey parameter, allowing them to execute arbitrary queries against the back-end database.

Business impact

This vulnerability is rated as High severity with a CVSS score of 8.3. Successful exploitation could have a severe impact on the business by compromising the confidentiality, integrity, and availability of data managed by the readarr application. An attacker could potentially extract sensitive user information, modify or delete critical application data leading to service disruption, or in some configurations, escalate privileges to compromise the underlying server. This poses a significant risk of data breach, operational disruption, and reputational damage.

Remediation

Immediate Action: Apply the security patches released by the vendor for readarr immediately to remediate the vulnerability. As a best practice, review database user permissions and ensure the application's database account operates under the principle of least privilege. It is also recommended to enable and centralize database query logging to assist in detecting and investigating potential exploitation attempts.

Proactive Monitoring: Security teams should actively monitor web server logs for suspicious requests to the /api/v1/wanted/cutoff endpoint, specifically looking for unusual or malformed data in the sortKey parameter. Database activity monitoring should be configured to alert on abnormal query structures, excessive data requests, or errors originating from the readarr application's user account.

Compensating Controls: If immediate patching is not feasible, implement a Web Application Firewall (WAF) with a ruleset configured to detect and block common SQL Injection attack patterns targeting the vulnerable endpoint and parameter. Restrict network access to the readarr web interface, limiting it to trusted IP addresses only.

Exploitation status

Public Exploit Available: false

Analyst recommendation

Given the High severity (CVSS 8.3) of this vulnerability and the potential for complete database compromise, organizations are strongly advised to treat this as a high-priority issue. The immediate application of vendor-supplied patches is the most effective course of action. While this CVE is not currently on the CISA KEV list, the critical nature of the flaw warrants urgent remediation to prevent potential data breaches and system compromise.