An unauthenticated SQL injection vulnerability in the Simple Flight Ticket Booking System 1.0 allows remote attackers to compromise the underlying database, posing a high risk to data integrity and confidentiality.

This vulnerability occurs due to improper neutralization of special elements used in an SQL command within the 'from' parameter of the SearchResultOneway.php script. An unauthenticated remote attacker can inject arbitrary SQL commands to manipulate database operations.

The exploitation of this flaw can result in unauthorized access to sensitive passenger and system data, potential data modification or deletion, and unauthorized administrative control over the database. Given the CVSS score of 7.3, this represents a high-severity risk that could lead to significant reputational damage and business disruption if the database is utilized for processing flight bookings or personal information.

Immediate Action: As no official patch is currently available, administrators should restrict access to the application via a firewall or by placing the application behind a VPN/authentication proxy. Developers should implement prepared statements with parameterized queries for the 'from' parameter in SearchResultOneway.php to eliminate the injection vector.

Proactive Monitoring: Review web server access logs for anomalous POST requests containing SQL keywords or characters such as single quotes, parentheses, or RLIKE/SLEEP functions directed at the SearchResultOneway.php endpoint.

Compensating Controls: Deploy a Web Application Firewall (WAF) configured with rules to detect and block common SQL injection patterns targeting the application's search parameters.

Public Exploit Available: Yes, a published proof-of-concept exists, as documented in the GitHub issue referenced by the researcher.

Given the availability of a public proof-of-concept and the trivial nature of the exploit, immediate attention is required. Organizations using this software must treat this as a high-priority risk and implement the suggested compensating controls or code-level mitigations to prevent unauthorized database access.