CVE-2024-41345: openflights · Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2024-41345, organizations should first identify all instances of openflights deployments and verify if they include the vulnerable php/trip.php component. Employ Content Security Policy (CSP) headers to restrict script execution sources and reduce the impact of potential XSS payloads. Additionally, enable HttpOnly and Secure flags on cookies to protect session tokens from theft via script access. Conduct security code reviews focusing on input handling in trip.php and related modules. Educate users about the risks of clicking suspicious links and consider deploying Web Application Firewalls (WAFs) with rules to detect and block reflected XSS attempts targeting the vulnerable endpoint. Monitor logs for unusual activity or error patterns indicative of attempted exploitation. Finally, stay updated with openflights project communications for official patches or updates addressing this vulnerability.
Description
openflights commit 5234b5b is vulnerable to Cross-Site Scripting (XSS) via php/trip.php