dbcve.org
Travel Management SystemApplication · Projectworlds

CVE-2025-9053

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-15
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 has been found in projectworlds Travel Management System 1.0. This vulnerability affects unknown code of the file /updatesubcategory.php. The manipulation of the argument t1/s1 leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may 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

SQL injection vulnerability in projectworlds Travel Management System 1.0 at /updatesubcategory.php. The t1 and s1 parameters are not properly sanitized, allowing remote attackers to inject arbitrary SQL commands. With CVSS 9.8 and public exploit availability, this can lead to complete database compromise including data exfiltration, authentication bypass, and potential remote code execution.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the t1 and s1 arguments in updatesubcategory.php. Apply input validation and least-privilege database accounts as defense-in-depth.

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. Confirm Travel Management System installation
    Search for files named 'updatesubcategory.php' or look for the projectworlds Travel Management System web directory on the server
    Affected if The file /updatesubcategory.php exists in the web root or a subdirectory of the travel management system
  2. Verify the application version
    Check version information in the application's about page, README file, or meta files, or inspect HTTP headers when accessing the application
    Affected if The installed version is exactly 1.0 (projectworlds Travel Management System)
  3. Confirm network accessibility of vulnerable endpoint
    Attempt to access http://[host]/updatesubcategory.php or check web server logs for requests to this endpoint
    Affected if The updatesubcategory.php endpoint is reachable via HTTP/HTTPS requests
  4. Check for input acceptance on vulnerable parameters
    Inspect the source code of updatesubcategory.php to verify the t1 and s1 parameters are accepted as user input without sanitization
    Affected if The t1 and s1 parameters are processed by the application without proper SQL sanitization or parameterized queries
  5. Determine if application uses unparameterized SQL queries
    Review the database queries in updatesubcategory.php or monitor database traffic when the t1 and s1 parameters are submitted
    Affected if Dynamic SQL queries concatenate the t1 or s1 parameters directly into SQL statements without prepared statements or escaping

A user is affected if they have projectworlds Travel Management System version 1.0 running with the updatesubcategory.php endpoint accessible over the network and the application uses dynamic SQL queries for the t1 and s1 parameters.

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 and s1 arguments in updatesubcategory.php. Apply input validation and least-privilege database accounts as defense-in-depth.

Fix this in Travel Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9053 — 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-9053 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