VulnerabilityPublished 8 Mar 2026Updated 10 Mar 2026

CVE-2026-3763: code-projects Simple Flight Ticket Booking System · Cross-site Scripting

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

Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% 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:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
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: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within 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: None: There is no impact to availability within 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 30 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-3763, organizations should immediately implement strict input validation and output encoding on all user-supplied data processed by showhistory.php and related components. Employing Content Security Policy (CSP) headers can help restrict the execution of unauthorized scripts. Web Application Firewalls (WAFs) should be configured to detect and block typical XSS attack patterns targeting this endpoint. Administrators should monitor web server logs for suspicious requests that may indicate exploitation attempts. User education about the risks of clicking untrusted links can reduce the likelihood of successful attacks. If feasible, isolating the booking system behind VPNs or restricting access to trusted networks can reduce exposure. Organizations should also engage with the vendor or community to obtain or develop patches and apply them promptly once available. Regular security assessments and code reviews focusing on input handling in showhistory.php are recommended to prevent similar issues.

Description

A vulnerability was found in code-projects Simple Flight Ticket Booking System 1.0. The affected element is an unknown function of the file showhistory.php. The manipulation results in cross site scripting. It is possible to launch the attack remotely. The exploit has been made public and could be used.

Impact

The primary impact of CVE-2026-3763 is the potential compromise of user session integrity and the execution of malicious scripts within the context of the affected web application. Attackers can exploit this vulnerability to steal session cookies, perform actions on behalf of authenticated users, or redirect users to malicious sites. While the confidentiality and availability impacts are minimal, the integrity of user data and trust in the booking system can be significantly affected. For organizations operating the Simple Flight Ticket Booking System, this could lead to reputational damage, loss of customer confidence, and potential regulatory scrutiny if user data is compromised. The fact that no authentication is required to exploit the vulnerability increases the risk of widespread attacks, especially if the system is publicly accessible. However, the need for user interaction somewhat limits automated exploitation. The absence of patches means organizations must rely on mitigations until an official fix is available.

Summary

CVE-2026-3763 identifies a cross-site scripting (XSS) vulnerability in the Simple Flight Ticket Booking System version 1.0 developed by code-projects. The vulnerability resides in an unspecified function within the showhistory.php file, which processes user input insufficiently, allowing malicious scripts to be injected and executed in the context of the victim's browser. This flaw enables remote attackers to craft URLs or input fields that, when accessed or interacted with by users, execute arbitrary JavaScript code. The vulnerability does not require any authentication or privileges, increasing its accessibility to attackers. However, user interaction is necessary to trigger the XSS payload, such as clicking a malicious link or viewing a compromised page. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), user interaction required (UI:P), and limited impact on integrity (VI:L) with no impact on confidentiality or availability. No patches or official fixes have been released yet, and while the exploit code has been publicly disclosed, there are no confirmed reports of exploitation in the wild. This vulnerability could be leveraged for session hijacking, phishing, or defacement attacks, potentially undermining user trust and data integrity within the booking system.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Mar 2026, 09:22 UTC

Technical details

References

Community reviews

Related threats