Vulnerabilidade de Injeção SQL (SQL Injection) em enquiry.php do projectworlds Travel Management System

Successful exploitation of CVE-2025-9924 could grant an attacker unauthorized access to sensitive data stored within the Travel Management System's database. This includes potentially accessing user credentials, financial information, travel itineraries, and other confidential details. An attacker could also modify or delete data, leading to data corruption and disruption of services. The remote nature of the vulnerability significantly expands the potential attack surface, making it accessible to a wide range of malicious actors. The SQL injection allows for arbitrary database queries, potentially enabling privilege escalation or even complete system compromise depending on database permissions.

Organizations utilizing the Travel Management System version 1.0, particularly those with sensitive travel data or financial information, are at significant risk. Shared hosting environments where multiple applications share the same database are especially vulnerable, as a successful exploit could impact other applications on the same server.

• php: Examine /enquiry.php for unsanitized input handling of the 't2' parameter. Look for patterns like $_GET['t2'] without proper validation.

if (isset($_GET['t2'])) {
  $t2 = $_GET['t2'];
  // Vulnerable code: no sanitization or validation
  $sql = "SELECT * FROM table WHERE column = '$t2';";
}

• generic web: Monitor access logs for unusual SQL injection attempts targeting /enquiry.php. Look for patterns containing SQL keywords like SELECT, UNION, INSERT, DELETE within the 't2' parameter. • generic web: Use curl to test the endpoint with a simple SQL injection payload: curl 'http://example.com/enquiry.php?t2=1' UNION SELECT 1,2,3 -- -

1. 2025-09-03Disclosure

   disclosure

1. Reservado2025-09-03
2. Publicada2025-09-03
3. EPSS atualizado2026-03-23

The primary mitigation for CVE-2025-9924 is to immediately upgrade the Travel Management System to version 1.0.1, which includes the necessary fix. If upgrading is not immediately feasible, consider implementing input validation and sanitization on the 't2' parameter within /enquiry.php to prevent malicious SQL code from being injected. Web application firewalls (WAFs) configured with rules to detect and block SQL injection attempts can provide an additional layer of defense. After upgrading, confirm the vulnerability is resolved by attempting a SQL injection attack on the /enquiry.php endpoint with a known malicious payload.