CVE-2025-9925: projectworlds Travel Management System · SQL Injection
Affects projectworlds Travel Management SystemSource CVE Database V5
Public exploit available · CVSS 6.9 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 3 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| projectworlds Travel Management System | Affected
| Fixed in– |
AI-suggested
Organizations should immediately audit their use of projectworlds Travel Management System 1.0 and restrict access to the /detail.php endpoint, especially the 'pid' parameter. Implementing a Web Application Firewall (WAF) with SQL injection detection rules can help block exploit attempts. Input validation and parameterized queries should be enforced in the application code to prevent injection. Regular database permission reviews should be conducted to ensure least privilege principles are applied. Monitoring logs for unusual query patterns or access to /detail.php can help detect exploitation attempts early. Organizations should also prepare incident response plans specific to data breaches involving travel management data.
Description
A vulnerability was found in projectworlds Travel Management System 1.0. This issue affects some unknown processing of the file /detail.php. The manipulation of the argument pid results in sql injection. The attack can be executed remotely. The exploit has been made public and could be used.