CVE-2026-5634
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 was identified in projectworlds Car Rental Project 1.0. Affected by this vulnerability is an unknown functionality of the file /book_car.php of the component Parameter Handler. The manipulation of the argument fname leads to sql injection. The attack can be initiated remotely. The exploit is publicly available and might 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 projectworlds Car Rental Project 1.0's /book_car.php file. The fname parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries through the Parameter Handler component.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Locate the vulnerable PHP fileSearch the web root directory for the file /book_car.php or paths containing 'book_car.php'. Use: find /var/www -name 'book_car.php' 2>/dev/null or dir /s /b C:\inetpub\wwwroot\book_car.php on Windows.Affected if The file exists in the web application directory tree.
-
Identify the application versionInspect the application for version metadata. Check README files, admin panels, or the source code header comments for 'Car Rental Project' version 1.0. Compare against the affected version range.Affected if The application is projectworlds Car Rental Project version 1.0.
-
Verify fname parameter handlingOpen book_car.php and locate the code handling the 'fname' parameter. Search for $_POST['fname'] or $_GET['fname'] and trace how this value is used in SQL queries.Affected if The fname parameter is directly interpolated into SQL queries without prepared statements or escaping functions.
-
Check for SQL sanitization functionsReview book_car.php for input validation functions like mysqli_real_escape_string, htmlspecialchars, PDO::prepare, or bindParam/bindValue used on the fname parameter before SQL execution.Affected if No sanitization or parameterized queries are found for the fname parameter in SQL contexts.
-
Test parameter injection safelySubmit a benign test payload to the fname parameter such as "test' OR '1'='1" as a query parameter or form input. Observe if the application returns unexpected results or SQL errors. Use only non-destructive probes.Affected if The application returns unexpected database results or exposes SQL error messages based on the test payload.
If the Car Rental Project 1.0 is deployed, book_car.php exists, and the fname parameter is used in SQL queries without prepared statements or escaping, the environment is likely affected by this SQL injection vulnerability.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements, or implement proper input validation and sanitization on the fname parameter before database execution.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5634 — 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-2026-5634 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