CVE-2026-3735
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 has been found in code-projects Simple Flight Ticket Booking System 1.0. Affected by this vulnerability is an unknown functionality of the file SearchResultOneway.php. Such manipulation of the argument from leads to sql injection. The attack can be launched 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 · moderate confidenceA SQL injection vulnerability exists in the SearchResultOneway.php file of Simple Flight Ticket Booking System 1.0. The 'from' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL code and potentially exfiltrate or manipulate the database.
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.
-
Locate the Simple Flight Ticket Booking System installationSearch the web server document root for directories containing 'flight' or 'booking' related files, or check known web application paths.Affected if The application files cannot be located on the system.
-
Verify the installed versionCheck for a version file, about page, or header/meta tags within the application that display the version number. Compare against the affected version 1.0.Affected if The installed version is 1.0.
-
Confirm presence of vulnerable fileLocate SearchResultOneway.php in the application directory structure, typically under a 'booking', 'search', or 'flight' subdirectory.Affected if SearchResultOneway.php is not found in the installation.
-
Inspect the 'from' parameter handlingOpen SearchResultOneway.php and examine how the 'from' parameter is handled - look for direct insertion into SQL queries without prepared statements, escaping functions, or input validation.Affected if The 'from' parameter is used directly in SQL queries without sanitization or parameterized queries.
-
Test parameter accessibilityIf the application is running, attempt to access the search functionality and observe if the 'from' parameter is accepted and processed by the SearchResultOneway.php endpoint.Affected if The 'from' parameter is processed by the application without validation.
A user is affected if Simple Flight Ticket Booking System version 1.0 is installed, SearchResultOneway.php exists, and the 'from' parameter is handled in SQL queries without sanitization or 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 (prepared statements) for all SQL queries that incorporate user input, specifically the 'from' argument in SearchResultOneway.php, and validate/sanitize all user inputs before database operations.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3735 — 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-3735 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