CVE-2025-9155

7.3

itsourcecode · Online Tour and Travel Management System

A SQL injection vulnerability exists in the Online Tour and Travel Management System 1.0, specifically within the forget_password.php file, allowing remote attackers to manipulate email arguments.

Executive summary

A remote SQL injection vulnerability in itsourcecode Online Tour and Travel Management System 1.0 poses a significant risk of unauthorized database interaction.

Vulnerability

This vulnerability is a SQL injection (CWE-89) flaw located in the forget_password.php file. The vulnerability is unauthenticated, meaning an attacker can trigger the flaw remotely without requiring prior system access.

Business impact

Successful exploitation of this vulnerability could allow an attacker to execute arbitrary SQL commands against the backend database. This may lead to unauthorized data disclosure, modification of sensitive information, or potential service disruption. With a CVSS score of 7.3, this flaw represents a high-severity risk that could compromise the integrity and confidentiality of the entire travel management platform.

Remediation

Immediate Action: As no official patch is currently identified, administrators should restrict network access to the application or implement strict input validation on the forget_password.php endpoint.

Proactive Monitoring: Monitor server logs for anomalous HTTP requests targeting the /user/forget_password.php file, specifically looking for characters indicative of SQL injection attempts.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules specifically configured to detect and block SQL injection patterns in incoming web traffic.

Exploitation status

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

Analyst recommendation

Given the availability of a public proof-of-concept and the unauthenticated nature of the vulnerability, organizations must treat this risk as urgent. Security teams should prioritize isolating the affected component until the vendor provides a formal security update to remediate the SQL injection flaw.

More itsourcecode CVEs

Sources

Originally found and disclosed by hjscs (VulDB User), per the CVE Program record.