VulnerabilityPublished 8 Mar 2026Updated 10 Mar 2026

CVE-2026-3708: code-projects Simple Flight Ticket Booking System · SQL Injection

Affects code-projects Simple Flight Ticket Booking SystemSource CVE Database V5

Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projectsSimple Flight Ticket Booking System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2026-3708, organizations should immediately implement parameterized queries or prepared statements in the /login.php script to prevent SQL injection. Input validation should be enforced rigorously, ensuring that the Username parameter only accepts expected characters and formats. Employing web application firewalls (WAFs) with SQL injection detection rules can provide an additional layer of defense against exploitation attempts. Monitoring and logging login attempts for unusual patterns can help detect early signs of attack. If possible, upgrade to a patched version of the Simple Flight Ticket Booking System once available, or apply vendor-provided fixes. In the interim, consider isolating the affected system from critical networks and restricting access to trusted IP addresses. Conduct regular security assessments and code reviews to identify and remediate similar vulnerabilities. Finally, educate development teams on secure coding practices to prevent recurrence of injection flaws.

Description

A security flaw has been discovered in code-projects Simple Flight Ticket Booking System 1.0. The impacted element is an unknown function of the file /login.php. Performing a manipulation of the argument Username results in sql injection. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks.

Impact

The impact of CVE-2026-3708 on organizations worldwide includes unauthorized access to sensitive customer information such as personal details and booking data, which can lead to privacy violations and regulatory non-compliance. Attackers exploiting this vulnerability could alter or delete booking records, causing operational disruptions and financial losses. The integrity of the booking system is compromised, potentially undermining customer trust and damaging the reputation of affected companies. Availability may also be affected if attackers execute destructive SQL commands or cause database errors. Since the vulnerability requires no authentication and can be exploited remotely, the attack surface is broad, increasing the risk to organizations that have deployed this software. The public release of exploit code further elevates the threat level, potentially leading to automated attacks and widespread exploitation if mitigations are not applied promptly.

Summary

CVE-2026-3708 identifies a SQL Injection vulnerability in the Simple Flight Ticket Booking System version 1.0 developed by code-projects. The vulnerability resides in the /login.php script, where the Username parameter is improperly sanitized, allowing attackers to inject malicious SQL code. This injection flaw can be exploited remotely without requiring authentication or user interaction, enabling attackers to manipulate backend database queries. Potential consequences include unauthorized retrieval of sensitive user data, modification or deletion of records, and possible disruption of booking services. The CVSS 4.0 base score of 6.9 reflects a medium severity, considering the network attack vector, low complexity, and no privileges or user interaction needed. Although no active exploits have been reported in the wild, the public availability of exploit code raises the likelihood of exploitation attempts. The vulnerability affects only version 1.0 of the product, and no official patches have been linked yet. The lack of secure coding practices in input handling is the root cause, emphasizing the need for parameterized queries and rigorous input validation. This flaw poses a significant risk to organizations using this software for flight ticket booking, potentially compromising customer data and operational integrity.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Mar 2026, 09:19 UTC

Technical details

References

Community reviews

Related threats