dbcve.org
Travel Management SystemApplication · Projectworlds

CVE-2025-9927

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was identified in projectworlds Travel Management System 1.0. The affected element is an unknown function of the file /viewpackage.php. Such manipulation of the argument t1 leads to sql injection. The attack may be performed from remote. The exploit is publicly available and might 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 confidence

Unauthenticated SQL injection vulnerability in projectworlds Travel Management System 1.0's /viewpackage.php file. The 't1' parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. With CVSS 9.8, this is easily exploitable and can lead to complete database compromise, including data exfiltration and potential system takeover.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the t1 parameter in viewpackage.php. If no vendor patch is available, temporarily disable the application or restrict network access until the fix is implemented.

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
Travel Management SystemApplication
Affected:= 1.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Projectworlds Travel Management System is installed
    Search the web root directory for the application files, typically looking for directories containing 'travel' or 'projectworlds' and the specific file viewpackage.php
    Affected if The application is present and accessible on the server
  2. Confirm the installed version is 1.0
    Locate any version file, README, or within the application source code check for version identifiers. Compare against the affected version range provided
    Affected if The installed version matches 1.0 exactly
  3. Verify viewpackage.php exists and is web-accessible
    Check for the presence of viewpackage.php in the web-accessible directory structure. This file should exist in the application's public web folder
    Affected if viewpackage.php exists and can be accessed via HTTP/HTTPS
  4. Inspect the t1 parameter handling in viewpackage.php
    Open viewpackage.php and locate code that handles the 't1' GET or POST parameter. Look for SQL query construction that uses this parameter without parameterized queries or input sanitization
    Affected if The 't1' parameter is used in dynamic SQL queries without prepared statements or proper escaping
  5. Test for unauthenticated SQL injection exposure
    Send a crafted request to viewpackage.php with the t1 parameter containing SQL injection syntax (such as a single quote or SQL boolean-based test). Observe if the application returns SQL error messages or behaves differently than expected
    Affected if The application returns SQL errors or displays unexpected behavior when special SQL characters are submitted in the t1 parameter
  6. Check if the application is exposed to the network
    Determine if the web server hosting the Travel Management System is accessible from untrusted networks or the internet without network-level access controls
    Affected if The vulnerable endpoint is reachable from unauthenticated remote attackers

A user is affected if they have Projectworlds Travel Management System version 1.0 running with viewpackage.php accessible and the t1 parameter used in unsanitized SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements for the t1 parameter in viewpackage.php. If no vendor patch is available, temporarily disable the application or restrict network access until the fix is implemented.

Fix this in Travel Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9927 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9927 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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