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

CVE-2025-8993

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 was found in itsourcecode Online Tour and Travel Management System 1.0. This affects an unknown part of the file /admin/expense_report.php. The manipulation of the argument from_date 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

A SQL injection vulnerability exists in the /admin/expense_report.php file of itsourcecode Online Tour and Travel Management System 1.0. The from_date parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries. This critical vulnerability (CVSS 9.8) could allow full database compromise including exfiltration of sensitive data or potential remote code execution depending on database configuration.

MitigationImmediate remediation requires replacing dynamic SQL queries with parameterized statements (prepared statements) for the from_date parameter. As a temporary defensive measure, implement input validation and consider deploying a WAF rule to block SQL injection payloads until the code fix is completed.

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 PHP file
    Search the web root for the file /admin/expense_report.php or run: find /var/www -name 'expense_report.php' 2>/dev/null
    Affected if The file exists in the application directory structure
  2. Confirm the application version
    Check application documentation, footer, or version file for 'Online Tour and Travel Management System' version 1.0. Also check if the application is derived from Mayurik or itsourcecode templates.
    Affected if The installed version is 1.0 or the application is identified as Mayurik/itsourcecode Tour and Travel Management System
  3. Verify admin interface accessibility
    Attempt to access /admin/ endpoint or check web server configuration for any rewrite rules or access controls protecting /admin/expense_report.php
    Affected if The /admin/expense_report.php endpoint is reachable without authentication or with low-privilege access
  4. Inspect source code for vulnerable parameter handling
    Examine the expense_report.php file and locate the from_date parameter handling. Look for unsanitized use of $_GET['from_date'] or $_POST['from_date'] in SQL queries without prepared statements or escaping.
    Affected if The code contains direct use of from_date parameter in SQL queries without parameterized statements or input sanitization
  5. Check database user privileges
    If code inspection confirms the vulnerability, determine the database user configured in the application's database connection file (commonly config.php, db.php, or similar). Check if the database user has excessive privileges beyond what the application requires.
    Affected if The application database user has privileges that could allow data exfiltration or, in some configurations, file operations or code execution

The environment is affected if the Mayurik/itsourcecode Online Tour and Travel Management System version 1.0 is installed and the /admin/expense_report.php file contains unsanitized from_date parameter handling in 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

Immediate remediation requires replacing dynamic SQL queries with parameterized statements (prepared statements) for the from_date parameter. As a temporary defensive measure, implement input validation and consider deploying a WAF rule to block SQL injection payloads until the code fix is completed.

Fix this in Online Tour \& Travel Management System Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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