CVE-2025-9926
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-9926 is a critical SQL injection vulnerability in Projectworlds Travel Management System version 1.0, specifically in the /viewsubcategory.php file. The vulnerability arises from improper handling and insufficient validation of the 't1' parameter, which is used directly in SQL queries without proper sanitization. This allows remote attackers to inject malicious SQL code, enabling unauthorized database access, data leakage, modification, or deletion. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to view, modify, or delete sensitive information. It can also cause data leakage, data tampering, and potentially full system compromise or service interruptions. The attack can be performed remotely without authentication, making it highly dangerous. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the 't1' parameter in the /viewsubcategory.php file for SQL injection flaws. A proof-of-concept payload uses a time-based blind SQL injection such as: t1=test' RLIKE SLEEP(5) AND 'OHPS'='OHPS&sbmt=Submit, which causes a delay in the database response, confirming the injection point. Tools like sqlmap can be used to automate detection, for example: sqlmap -u "http://<target>/viewsubcategory.php" --data="t1=test" --technique=T --time-sec=5. Additionally, attackers may use Google Dorking with the query "inurl:viewsubcategory.php" to identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implementing strict input validation and filtering on the 't1' parameter to ensure it conforms to expected formats. 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine database operations. 4) Conducting regular security audits to detect and fix vulnerabilities promptly. If possible, replace the affected component or upgrade to a version without this vulnerability. [1, 3]