Simple Flight Ticket Booking SystemApplication · Carmelo

CVE-2026-3723

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A security flaw has been discovered in code-projects Simple Flight Ticket Booking System 1.0. This affects an unknown function of the file /Admindelete.php. The manipulation of the argument flightno results in sql injection. The attack may be performed from remote. The exploit has been released to the public and may 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 · high confidence

SQL injection vulnerability in Simple Flight Ticket Booking System 1.0's Admindelete.php file allows remote attackers to inject malicious SQL queries via the 'flightno' parameter. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially leading to unauthorized data access, modification, or complete system compromise.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in Admindelete.php, apply input validation on the flightno parameter, and conduct a broader security audit of the application for similar SQL injection vulnerabilities.

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
Simple Flight Ticket Booking SystemApplication
Affected:= 1.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed version of the Flight Ticket Booking System
    Locate and inspect any version files, headers, or metadata files in the application installation directory that indicate the software version. Check README files, changelogs, or the main index.php for version information.
    Affected if The installed version is exactly 1.0 of Carmelo Simple Flight Ticket Booking System
  2. Verify Admindelete.php exists in the application
    Search the web root directory for the file Admindelete.php. Common locations may include /admin/, /php/, or the root web directory. Use file system search or check the application's file structure.
    Affected if The file Admindelete.php is present in the application installation
  3. Check if the flightno parameter is processed unsafely
    Open Admindelete.php and inspect the code handling the 'flightno' parameter. Look for direct insertion of the parameter into SQL queries without using prepared statements, parameter binding, or input sanitization functions.
    Affected if The code shows direct use of $_GET['flightno'] or $_POST['flightno'] concatenated into SQL queries without escaping or parameterized queries
  4. Confirm the vulnerable endpoint is accessible
    Attempt to access Admindelete.php via HTTP/HTTPS request (e.g., GET or POST to the file URL with a test flightno parameter). Verify the application responds and the parameter is processed.
    Affected if The Admindelete.php endpoint is reachable and processes the flightno parameter without validation

A system is affected if it runs Simple Flight Ticket Booking System version 1.0 AND contains the Admindelete.php file with the unprotected flightno parameter that gets inserted directly into SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements in Admindelete.php, apply input validation on the flightno parameter, and conduct a broader security audit of the application for similar SQL injection vulnerabilities.

Fix this in Simple Flight Ticket Booking System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3723 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3723 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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