CVE-2025-6907
BaseFortify
Publication date: 2025-06-30
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-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-6907 is a critical SQL injection vulnerability in the Car Rental System version 1.0, specifically in the /book_car.php file. It occurs because the application does not properly validate or sanitize the 'fname' parameter, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, data modification or deletion, and potentially full system compromise or service disruption. Attackers can remotely exploit this flaw without authentication, which threatens the confidentiality, integrity, and availability of the system and its data, potentially causing severe security breaches and business continuity issues. [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 identifying if the /book_car.php endpoint is accessible and vulnerable to SQL injection via the 'fname' parameter. One method is to perform a targeted test by sending crafted HTTP requests with SQL injection payloads in the 'fname' parameter and observing the response for SQL errors or unexpected behavior. Additionally, Google dorking can be used to find vulnerable targets by searching for "inurl:book_car.php". Example commands to test the vulnerability include using curl or sqlmap: 1) curl -G "http://target.com/book_car.php" --data-urlencode "fname=' OR '1'='1" 2) sqlmap -u "http://target.com/book_car.php?fname=test" --risk=3 --level=5 --batch These commands attempt to inject SQL code via the 'fname' parameter to detect if the system is vulnerable. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements (parameterized queries) to ensure user inputs like 'fname' are treated as data, not executable SQL code. 2) Applying strict input validation and filtering to enforce expected data formats for the 'fname' parameter. 3) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 4) Conducting regular security audits to detect and remediate vulnerabilities promptly. If possible, replace the affected component with an alternative product. These measures help prevent exploitation of the SQL injection vulnerability in /book_car.php. [3, 2]