CVE-2025-7167
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-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. |
| 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?
CVE-2025-7167 is a SQL injection vulnerability in version 1.0 of the code-projects Responsive Blog Site, specifically in the category.php file. The vulnerability arises because the 'id' parameter is used directly in SQL queries without proper sanitization or parameterization, allowing attackers to inject malicious SQL code. This can lead to unauthorized access, data theft, data modification, deletion, or even execution of server commands by manipulating the database queries remotely. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to sensitive data, theft or modification of data, deletion of data, and potentially complete system compromise. Attackers can remotely exploit this flaw to manipulate the database, affecting the 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 the /category.php file for SQL injection. A common tool to detect such SQL injection vulnerabilities is sqlmap. For example, you can run the command: sqlmap -u "http://<target>/category.php?id=1" --batch -dbs This command attempts to detect and exploit SQL injection on the 'id' parameter and enumerate databases if vulnerable. Additionally, attackers can be identified by monitoring for unusual requests to URLs containing 'category.php' with suspicious or malformed 'id' parameters. Google dorking such as searching for 'inurl:category.php' can help identify potentially vulnerable targets externally. [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 before using it in SQL queries, for example, using intval() in PHP. Better yet, refactor the code to use prepared statements with parameter binding to safely handle user input and prevent SQL injection. Additionally, apply the principle of least privilege to database users and implement proper error handling to avoid exposing detailed database errors to users. [2, 3]