Overview
The CVE-2025-50983 is a significant vulnerability that was discovered in the readarr software version 0.4.15.2787. This vulnerability primarily affects those who use readarr for managing their books and could lead to potential system compromise or data leakage. In the ever-growing field of cybersecurity, such vulnerabilities can pose severe threats to the integrity, confidentiality, and availability of data if not resolved promptly. The severity of this vulnerability highlights the importance of regular system updates and thorough security practices.
Vulnerability Summary
CVE ID: CVE-2025-50983
Severity: High (8.3)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Potential system compromise or data leakage
Affected Products
Escape the Surveillance Era
Most apps won’t tell you the truth.
They’re part of the problem.
Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.
Ameeba Chat gives you a way out.
- • No phone number
- • No email
- • No personal info
- • Anonymous aliases
- • End-to-end encrypted
Chat without a trace.
Product | Affected Versions
readarr | 0.4.15.2787
How the Exploit Works
The exploit takes advantage of a SQL Injection vulnerability in the sortKey parameter of the GET /api/v1/wanted/cutoff API endpoint in readarr 0.4.15.2787. The endpoint fails to sanitize user-supplied input correctly, allowing attackers to inject and execute arbitrary SQL commands against the backend SQLite database. Attackers can use tools such as Sqlmap for exploitation via stacked queries, demonstrating that the parameter can be misused to run arbitrary SQL statements. A heavy query can be executed using SQLite’s RANDOMBLOB() and HEX() functions to simulate a time-based payload, indicating deep control over database interactions.
Conceptual Example Code
Below is a conceptual example of how the vulnerability might be exploited. This is a sample HTTP GET request:
GET /api/v1/wanted/cutoff?sortKey=1%3BDELETE+FROM+users HTTP/1.1
Host: target.example.comThis request attempts to exploit the vulnerability by inserting a SQL command (`1;DELETE FROM users`) in the sortKey parameter. If successful, this could lead to deletion of all users from the ‘users’ table in the database.
