CVE-2025-58450
BaseFortify
Publication date: 2025-09-08
Last updated on: 2025-09-09
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| prest | prest | 2.0.0-rc2 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection issue in pREST (PostgreSQL REST), an API that provides an application layer on top of a PostgreSQL database. Versions prior to 2.0.0-rc3 do not adequately validate inputs, allowing attackers to inject malicious SQL code. This can lead to unauthorized database queries or manipulation. The issue is fixed in version 2.0.0-rc3 with improved validation.
How can this vulnerability impact me? :
The SQL injection vulnerability can allow attackers to execute arbitrary SQL commands on the database, potentially leading to unauthorized data access, data modification, or deletion. This can compromise the confidentiality, integrity, and availability of the database and the application relying on it.
What immediate steps should I take to mitigate this vulnerability?
Upgrade pREST to version 2.0.0-rc3 or later, as this version contains a patch that mitigates the SQL injection vulnerability.