CVE-2026-3708 is a SQL injection flaw in code-projects Simple Flight Ticket Booking System 1.0, scored 7.3 (High) in the CVE record. The weak spot is the Username parameter in /login.php. The record lists no fixed version, so take the app off public networks, and if you maintain the code, replace string built queries with prepared statements.
What's affected
- Product: code-projects Simple Flight Ticket Booking System
- Affected version: 1.0
- Location:
/login.php - Input at issue: the Username parameter
- Fixed version: none listed in the record
The record says the exploit has been disclosed publicly. It does not say the flaw is being used in attacks, and the CVE is not in the CISA Known Exploited Vulnerabilities catalog.
Check the project page or vendor site for a newer release.
How to check if you're exposed
Start with whether the app exists in your estate at all. Sample and student projects from code listing sites often end up on a spare server and stay there.
find /var/www /srv /opt /home -name "login.php" 2>/dev/null
If the file turns up, confirm the app is version 1.0 and whether the web server answers from outside your network. Then open that file and read how it builds its database query. If the request value is joined into the SQL text instead of passed as a bound parameter, the weakness is present.
What to do now
- Find every copy of the app, including staging and backup hosts.
- If it faces the internet, take it offline or put it behind a VPN or an allow list of known addresses now.
- Check the project page for a patched release. If none exists, plan to retire the app or fix the query yourself.
- If you keep it, change the affected query to use prepared statements with bound parameters, and give the database account only the rights the app needs.
- Review web server and database logs for odd requests to the affected page.
Why it matters
The record files this under CWE-74 and CWE-89. The weakness is old and well understood. A query is assembled by joining strings, so characters in the input are read as SQL rather than as data. Prepared statements keep the two apart, because the database receives the command and the values separately.
Sample projects are written to teach a feature, not to hold real records. If one has ended up in production, the safest fix is often to replace it or put it where only trusted users can reach it.
Quick check
Is there a patch for this?
The record lists no fixed version. Check the project page or vendor site, and until you find one, limit network access to the app.
Does a dependency scan find this?
No. The flaw is in the app's own PHP code, not in a library. Code review or a static code scan finds this kind of issue, and the dependency scan covers the packages around it.
Sources
Last reviewed: 19 October 2026.
