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

CVE-2025-8983

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 identified in itsourcecode Online Tour and Travel Management System 1.0. This issue affects some unknown processing of the file /admin/operations/expense.php. The manipulation of the argument expense_for leads to sql injection. The attack may 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 itsourcecode Online Tour and Travel Management System 1.0 allows remote attackers to inject malicious SQL queries through the expense_for parameter in /admin/operations/expense.php. The lack of input sanitization or parameterized queries enables manipulation of database queries, potentially leading to unauthorized data access, modification, or complete database compromise.

MitigationReplace direct string concatenation in SQL queries with parameterized queries (prepared statements) to neutralize the injection vector. Apply vendor patch if available; otherwise, implement input validation, output encoding, and restrict database user privileges as compensating controls.

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
    Locate the web application's document root directory and verify the presence of itsourcecode Online Tour and Travel Management System or Mayurik Online Tour & Travel Management System. Check for typical file paths such as /var/www/html/, /www/, or C:\inetpub\wwwroot\ depending on your OS.
    Affected if The application directory exists and contains tour/travel management system files.
  2. Verify the application version
    Inspect version files, readme files, or footer files within the application root for the exact version number 1.0. Check files like version.php, README.txt, or any copyright footer in index.php.
    Affected if The installed version is exactly 1.0.
  3. Confirm the vulnerable file exists
    Check for the presence of the file /admin/operations/expense.php within the application directory. This is the specific file containing the SQL injection vulnerability.
    Affected if The file admin/operations/expense.php exists in the application.
  4. Verify the expense_for parameter is accessible
    Access the URL endpoint /admin/operations/expense.php through a web browser or curl request. Confirm the page loads and accepts the expense_for parameter as part of the request (GET or POST).
    Affected if The page loads and the expense_for parameter is processed by the application.
  5. Check if the application handles the expense_for input safely
    Examine the source code of expense.php to determine if the expense_for parameter is used in SQL queries without parameterized queries or input sanitization. Search for SQL query patterns like 'SELECT' or 'INSERT' that directly concatenate the expense_for variable.
    Affected if The code contains direct SQL query construction using the expense_for parameter without prepared statements or sanitization functions.

A user is affected if the Mayurik Online Tour and Travel Management System version 1.0 is installed, the file admin/operations/expense.php exists, and the expense_for parameter is handled without parameterized queries or input sanitization in the code.

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 direct string concatenation in SQL queries with parameterized queries (prepared statements) to neutralize the injection vector. Apply vendor patch if available; otherwise, implement input validation, output encoding, and restrict database user privileges as compensating controls.

Fix this in Online Tour \& Travel Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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