CVE-2025-6579
BaseFortify
Publication date: 2025-06-24
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 |
|---|---|---|
| anisha | car_rental_system | 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-6579 is a critical SQL injection vulnerability in version 1.0 of the code-projects Car Rental System, specifically in the /message_admin.php file. The vulnerability occurs because the 'message' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized database access, data modification or deletion, and exposure of sensitive information. The attack can be performed remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, data tampering, full system control by attackers, and potential service disruption. Since it can be exploited remotely without authentication, it poses a high risk to the confidentiality, integrity, and availability of the 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 /message_admin.php endpoint for SQL injection in the 'message' parameter. A common method is to use a time-based blind SQL injection payload such as: message=11111' AND (SELECT 1941 FROM (SELECT(SLEEP(5)))Txxu) AND 'oNCI'='oNCI&send=Send Message. Tools like sqlmap can be used to automate detection and exploitation attempts. Additionally, Google dorking with queries like inurl:message_admin.php can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implement strict input validation and filtering to ensure inputs conform to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like root or admin for routine operations. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, replace the affected component with an alternative product. [2, 3, 1]