dbcve.org
Online Tour \& Travel Management SystemApplication · Mayurik

CVE-2025-8970

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 found in itsourcecode Online Tour and Travel Management System 1.0. This affects an unknown part of the file /admin/operations/booking.php. The manipulation of the argument ID leads to sql injection. It is possible to initiate 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 · high confidence

SQL injection vulnerability in itsourcecode Online Tour and Travel Management System 1.0 allows remote attackers to inject malicious SQL queries via the ID parameter in /admin/operations/booking.php. The lack of input sanitization enables attackers to manipulate database queries, potentially leading to unauthorized data access or complete database compromise.

MitigationImplement parameterized queries (prepared statements) for all database operations, particularly for the ID parameter in booking.php. If no vendor patch is available, restrict access to the admin panel through network-level controls or deploy a Web Application Firewall as an interim measure.

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. Locate the vulnerable application file
    Check if the file /admin/operations/booking.php exists in the web root directory of the installed application
    Affected if The file booking.php exists in the /admin/operations/ directory and the application is Mayurik Online Tour & Travel Management System version 1.0
  2. Verify the application version
    Check the application's version information - typically found in a README file, about page, or version metadata within the source code
    Affected if The installed version is Mayurik Online Tour & Travel Management System version 1.0 exactly
  3. Confirm the vulnerable parameter is accessible
    Verify the web server is serving the /admin/operations/booking.php endpoint and the ID parameter is accepted (e.g., by visiting the URL or reviewing access logs)
    Affected if The booking.php page is accessible and accepts an ID parameter without authentication restrictions
  4. Check for input sanitization in the code
    Examine the source code of booking.php and locate the line handling the ID parameter - look for whether the ID value is used directly in SQL queries without prepared statements or escaping functions
    Affected if The ID parameter from $_GET or $_POST is directly concatenated into SQL queries without using parameterized queries, mysqli_prepare, or similar sanitization functions

The environment is affected if the application is Mayurik Online Tour & Travel Management System version 1.0, the file /admin/operations/booking.php exists, and the ID parameter is processed without prepared statements or input sanitization in the database 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

Implement parameterized queries (prepared statements) for all database operations, particularly for the ID parameter in booking.php. If no vendor patch is available, restrict access to the admin panel through network-level controls or deploy a Web Application Firewall as an interim measure.

Fix this in Online Tour \& 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-8970 — 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-8970 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