CVE-2025-9928
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 security flaw has been discovered in projectworlds Travel Management System 1.0. The impacted element is an unknown function of the file /viewcategory.php. Performing manipulation of the argument t1 results in sql injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may be exploited.
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 confidenceA SQL injection vulnerability exists in projectworlds Travel Management System 1.0 within the /viewcategory.php file. The t1 parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL code. The vulnerability has a public exploit and can be triggered remotely.
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.
-
Confirm Travel Management System installationIdentify if Projectworlds Travel Management System version 1.0 is installed in your environment. Check application directories, deployment manifests, or software inventory for this specific product and version.Affected if The software is not Projectworlds Travel Management System version 1.0, then this CVE does not apply.
-
Locate the vulnerable PHP fileSearch for the file /viewcategory.php in your web application's document root or source code directory. This is the specific file containing the SQL injection vulnerability.Affected if The file /viewcategory.php does not exist in your deployment, then this CVE does not apply.
-
Verify the t1 parameter is processedExamine how the t1 parameter is handled in viewcategory.php. Look for code that retrieves the t1 parameter from GET or POST requests and passes it directly to SQL queries without sanitization or use of prepared statements.Affected if The t1 parameter is not used in SQL queries within this file, or if the code uses parameterized queries/prepared statements for this parameter, then the vulnerability is not present.
-
Confirm network accessibilityDetermine if the application is accessible over the network. The vulnerability can be triggered remotely, so an exposed application with this file is potentially exploitable.Affected if The application is not network-accessible but the vulnerable file exists, the risk is limited to local attackers only.
You are affected if you are running Projectworlds Travel Management System version 1.0 with the file /viewcategory.php present and the t1 parameter being used in unsanitized SQL queries.
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 parameterized queries or prepared statements in /viewcategory.php for the t1 parameter, and validate/sanitize all user inputs before database operations.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9928 — 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-9928 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