CVE-2025-7166
BaseFortify
Publication date: 2025-07-08
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| fabian | responsive_blog_site | 1.0 |
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. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-7166 is a critical SQL injection vulnerability in the Responsive Blog Site 1.0, specifically in the /single.php file. It occurs because the application uses the "id" parameter from user input directly in SQL queries without proper sanitization or parameterization. This allows attackers to inject malicious SQL code remotely, manipulating database queries to access, modify, or delete data unauthorizedly. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to the database, data theft, data modification, deletion of database contents, and potentially complete system compromise. Attackers can remotely exploit this flaw to manipulate SQL queries, which may result in loss of confidentiality, integrity, and availability of the affected system. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable URL parameter 'id' in /single.php for SQL injection. A common approach is to use automated tools like sqlmap. For example, you can run the command: sqlmap -u "http://<target>/single.php?id=1" --batch -dbs to check if the parameter is vulnerable to SQL injection. Additionally, attackers may be identified by monitoring for suspicious requests targeting URLs with 'single.php?id=' parameters, or by using Google dorking with queries like "inurl:single.php" to find exposed instances. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with a secure alternative if possible. If continuing to use the software, apply input validation by forcing the 'id' parameter to be an integer (e.g., using intval in PHP) and avoid direct concatenation of user input into SQL queries. Implement prepared statements with parameter binding to safely handle user inputs. Additionally, apply the principle of least privilege to database users and ensure proper error handling to avoid exposing database errors to users. [2, 3]