CVE-2025-9925
BaseFortify
Publication date: 2025-09-03
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| projectworlds | travel_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-9925 is a critical SQL injection vulnerability in Projectworlds Travel Management System version 1.0, specifically in the /detail.php file. The vulnerability occurs because the 'pid' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL queries. This can lead to unauthorized access to the database, enabling attackers to retrieve, modify, or delete sensitive data without authentication. The vulnerability can be exploited remotely and has publicly available proof-of-concept exploits. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can result in unauthorized access to sensitive information, data leakage, data modification, or deletion. It can compromise the confidentiality, integrity, and availability of the system and its data. Attackers can remotely execute arbitrary SQL commands without authentication, potentially leading to full system compromise and service disruption. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'pid' parameter in the /detail.php file for SQL injection using various techniques such as boolean-based blind, error-based, time-based blind, and UNION query injections. Example payloads include: - Boolean-based blind: pid=1' AND 9902=9902 AND 'yEpK'='yEpK - Error-based: pid=1' OR (SELECT 5347 FROM(SELECT COUNT(*),CONCAT(0x71716b7071,(SELECT (ELT(5347=5347,1))),0x7162707071,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a) AND 'ldqY'='ldqY - Time-based blind: pid=1' AND (SELECT 9332 FROM (SELECT(SLEEP(5)))UMxS) AND 'UBIW'='UBIW - UNION query: pid=-9310' UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,CONCAT(0x71716b7071,0x616a5250426b694445667a41627a54714473576d4d4a55615574706d6862775a4478784e6161636f,0x7162707071),NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL-- - Additionally, automated tools like sqlmap can be used to confirm the presence of the vulnerability by targeting the 'pid' parameter in /detail.php. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements with parameter binding to separate SQL code from user input. - Enforce strict input validation and filtering to ensure inputs conform to expected formats. - Minimize database user permissions by avoiding use of high-privilege accounts such as 'root' or 'admin' for routine database operations. - Conduct regular security audits to detect and address vulnerabilities promptly. If possible, replace the affected software with an alternative product as no known countermeasures or patches are reported. [2, 3]