Online Tour \& Travel Management SystemApplication · Mayurik

CVE-2025-8967

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-14
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 determined in itsourcecode Online Tour and Travel Management System 1.0. Affected is an unknown function of the file /admin/operations/packages.php. The manipulation of the argument pname leads to sql injection. It is possible to launch the attack 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 · moderate confidence

SQL injection vulnerability in itsourcecode Online Tour and Travel Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the pname parameter in /admin/operations/packages.php. The lack of input sanitization enables attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements to properly sanitize the pname parameter and other user inputs.

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
Online Tour \& 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 the application is installed
    Check for the presence of itsourcecode Online Tour and Travel Management System or Mayurik Online Tour & Travel Management System in your web server directories. Look for the /admin/operations/packages.php file.
    Affected if The application and vulnerable file exist in the environment
  2. Verify the version is 1.0
    Check the version information of the installed Online Tour and Travel Management System. Compare against version 1.0 which is listed as affected.
    Affected if The installed version is exactly 1.0
  3. Confirm the vulnerable parameter exists
    Locate and inspect the /admin/operations/packages.php file. Look for PHP code that handles the pname parameter without using prepared statements or parameter binding.
    Affected if The pname parameter is processed in SQL queries without sanitization or parameterized queries
  4. Check admin access exposure
    Verify that the /admin/operations/packages.php endpoint is accessible over the network (it is an admin interface, so check if network access controls permit reachability to this path).
    Affected if The admin interface is accessible from where an attacker could send requests
  5. Test for SQL injection vulnerability
    If you have authorization, send a test request to packages.php with a pname parameter value containing SQL injection syntax (such as a single quote) and observe if SQL errors are returned or if the query behavior changes unexpectedly.
    Affected if The pname parameter reflects SQL syntax in database errors or alters query behavior without proper sanitization

If the Online Tour and Travel Management System version 1.0 is installed and the /admin/operations/packages.php endpoint handles the pname parameter without prepared statements, the environment is vulnerable to CVE-2025-8967.

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 or prepared statements to properly sanitize the pname parameter and other user inputs.

Fix this in Online Tour \& Travel Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8967 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