CVE-2025-6907
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability classified as critical was found in code-projects Car Rental System 1.0. This vulnerability affects unknown code of the file /book_car.php. The manipulation of the argument fname leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in Car Rental System 1.0 allows remote attackers to execute arbitrary SQL commands through the fname parameter in /book_car.php. The lack of parameterized queries or input sanitization enables attackers to manipulate database queries, potentially leading to data exfiltration, authentication bypass, or complete system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Car Rental System installationLocate the web application directory and verify the presence of Car Rental System files, particularly looking for /book_car.php in the web root. Check application version by examining README files, headers, or footer strings mentioning 'Car Rental System 1.0' or 'Anisha'.Affected if The application is installed and exposed on the server, particularly if it is Car Rental System version 1.0
-
Verify the vulnerable file existsConfirm that /book_car.php exists in the web application directory. This is the specific file containing the vulnerable fname parameter handling.Affected if /book_car.php is present in the web application root
-
Check web server exposureDetermine if the application is accessible over the network by checking web server configuration (Apache/nginx/IIS) and verifying the application responds to HTTP requests on configured ports.Affected if The application is accessible via HTTP/HTTPS from network locations
-
Inspect the vulnerable parameter handlingExamine the source code of /book_car.php and locate the database query handling for the 'fname' parameter. Look for direct inclusion of $_POST['fname'] or $_GET['fname'] in SQL statements without using prepared statements, parameter binding, or input sanitization functions.Affected if The code shows direct string concatenation of the fname parameter into SQL queries without parameterized queries or proper escaping
-
Check database user privilegesReview the database configuration file (such as config.php, db.php, or similar) to determine what database credentials the application uses and whether the database user has elevated privileges that could be exploited.Affected if The application connects to a database with privileges that could allow data exfiltration or further compromise
A user is affected if they have Anisha Car Rental System version 1.0 running with /book_car.php accessible over the network and the fname parameter is handled via direct string concatenation in SQL queries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement prepared statements/parameterized queries for all database interactions, particularly in /book_car.php for the fname parameter and similar user inputs across the application. Consider input validation and output encoding as defense-in-depth measures.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6907 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6907 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data