CVE-2025-9925
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in projectworlds Travel Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the pid parameter in /detail.php. The vulnerability is exploitable remotely and a public exploit exists.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Travel Management System installationSearch for files or directories containing 'travel' or 'projectworlds' on the web server. Common paths may include /var/www/, /htdocs/, or C:\inetpub\wwwroot\. Check for the presence of detail.php file.Affected if The application files are found and detail.php exists in the web-accessible directory
-
Verify the installed versionCheck version.php, README.txt, or any version file within the installation directory for the exact version number. If no version file exists, compare the file timestamps or hash against a known 1.0 release.Affected if The installed version is exactly 1.0
-
Confirm detail.php accepts the pid parameterAccess the detail.php page via HTTP request and verify it accepts a 'pid' parameter. For example: GET /detail.php?pid=1. Check if the application processes this parameter in database queries.Affected if The detail.php page responds to pid parameter requests and appears to use it in database operations
-
Test for SQL injection vulnerabilitySubmit a single quote (') or SQL-specific payloads (e.g., ' OR '1'='1) as the pid parameter value. Observe if the application returns database errors, unexpected behavior, or differing responses compared to valid numeric input.Affected if The application returns SQL syntax errors or exhibits unexpected behavior when special characters are submitted in the pid parameter
The system is affected if Projectworlds Travel Management System version 1.0 is installed, detail.php is accessible, and the pid parameter exhibits SQL injection behavior when tested with malicious input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL queries with prepared statements/parameterized queries for the pid parameter in /detail.php, and implement input validation on all user-supplied data before using them in database operations.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9925 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9925 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data