CVE-2026-5645
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 weakness has been identified in projectworlds Car Rental System 1.0. Affected by this vulnerability is an unknown functionality of the file /pay.php of the component Parameter Handler. Executing a manipulation of the argument mpesa can lead to sql injection. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks.
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 · moderate confidenceSQL injection vulnerability in projectworlds Car Rental System 1.0 allows remote attackers to inject malicious SQL queries via the mpesa parameter in /pay.php. The vulnerability exists in the Parameter Handler component and can be exploited without authentication.
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.
-
Confirm projectworlds Car Rental System is deployedInspect the web application files, headers, or documentation to verify the application is projectworlds Car Rental System. Look for application name, branding, or copyright identifiers in the source code.Affected if The deployed application is projectworlds Car Rental System
-
Verify application version is 1.0Check for version indicators in version files, about pages, config files, or the application root directory. Compare the installed version against the affected version 1.0.Affected if The installed version is 1.0
-
Locate pay.php in the web directorySearch the web server document root for the pay.php file. This file is part of the payment processing functionality and should exist in the application directory.Affected if The pay.php file exists in the application
-
Identify mpesa parameter usage in pay.phpOpen pay.php and search for code handling the 'mpesa' parameter. Look for $_GET['mpesa'], $_POST['mpesa'], or similar references that process this parameter.Affected if The mpesa parameter is processed in pay.php
-
Check Parameter Handler for SQL query constructionExamine how the mpesa parameter is used in database queries within pay.php. Look for direct concatenation of the parameter value into SQL statements without prepared statements or parameterized queries.Affected if The mpesa parameter is directly inserted into SQL queries without parameterization
The environment is affected if it runs projectworlds Car Rental System version 1.0 with the pay.php file containing mpesa parameter handling that constructs SQL queries without prepared statements.
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 parameterized queries or prepared statements for all database operations involving the mpesa parameter. Apply input validation and sanitization, and consider deploying a WAF as a defense-in-depth measure.
- 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-5645 — 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-5645 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