pREST has a Systemic SQL Injection Vulnerability in github.com/prest/prest

The SQL Injection vulnerability in pREST presents a significant risk. An attacker could leverage this flaw to bypass authentication mechanisms, extract sensitive data such as user credentials, financial information, or proprietary business data stored in the database. Successful exploitation could lead to complete database compromise, allowing the attacker to modify or delete data, or even execute arbitrary commands on the server. The potential blast radius extends to any system relying on pREST for data storage and retrieval, making it a critical concern for organizations utilizing this project. While no direct precedent is immediately obvious, SQL Injection vulnerabilities are consistently among the most exploited web application flaws.

Organizations and developers utilizing pREST for data storage and retrieval are at risk. This includes those deploying pREST in production environments, particularly those with sensitive data stored in the database. Applications relying on pREST as a backend service are also vulnerable.

• linux / server:

journalctl -u prest -g "SQL injection"

• generic web:

curl -I <prest_endpoint> | grep -i "SQL injection"

1. 2025-09-17Disclosure

   disclosure

1. आरक्षित2025-09-01
2. प्रकाशित2025-09-17
3. संशोधित2026-03-03
4. EPSS अद्यतन2026-03-23

The primary mitigation for CVE-2025-58450 is to immediately upgrade to version 2.0.0-rc3 or later. If upgrading is not immediately feasible due to compatibility issues or breaking changes, consider implementing temporary workarounds. Input validation and sanitization on all user-supplied data is crucial. Web Application Firewalls (WAFs) configured with rules to detect and block SQL Injection attempts can provide an additional layer of defense. Monitor database logs for suspicious SQL queries that might indicate an ongoing attack. Consider implementing a least-privilege database user account for pREST to limit the potential damage from a successful exploit.