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

CVE-2025-8969

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 has been found in itsourcecode Online Tour and Travel Management System 1.0. Affected by this issue is some unknown functionality of the file /admin/approve_user.php. The manipulation of the argument ID leads to sql injection. The attack may be launched 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/approve_user.php. The application fails to properly sanitize user input before using it in database queries, enabling attackers to manipulate SQL statements and potentially exfiltrate, modify, or delete database contents.

MitigationImplement parameterized queries (prepared statements) for all database operations in approve_user.php, specifically for the ID parameter. Alternatively, use a properly sanitized input validation layer and ensure least-privilege database accounts.

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. Identify if the application is installed
    Locate the web application files. Common paths include /var/www/html/, /www/, or C:\inetpub\wwwroot\. Look for folders named 'admin', 'tour', 'travel', or 'itsourcecode'.
    Affected if The Online Tour and Travel Management System files are present on the server.
  2. Verify the application version
    Check for a version file, README, or any file containing version information in the application root directory. Alternatively, view the page source of any accessible page for version comments.
    Affected if The installed version is exactly 1.0.
  3. Confirm the vulnerable file exists
    Locate and verify the presence of /admin/approve_user.php in the web application directory. This file handles user approval operations.
    Affected if The file /admin/approve_user.php exists in the installation.
  4. Check if the admin interface is accessible
    Attempt to access the /admin/ directory or the specific approve_user.php file via HTTP from the web server. Check if the application responds without authentication or with valid admin credentials.
    Affected if The admin module and approve_user.php are accessible (with or without authentication).
  5. Inspect the source code for the vulnerability
    Open approve_user.php and examine how the ID parameter is handled in database queries. Look for unsanitized $_GET or $_POST['id'] usage directly in SQL statements without prepared statements or escaping functions.
    Affected if The ID parameter is used directly in SQL queries without parameterized queries, input sanitization, or escaping functions.

You are affected if the Online Tour and Travel Management System version 1.0 is installed, the /admin/approve_user.php file exists, and the ID parameter in that file is used directly in SQL queries without proper sanitization or prepared statements.

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 in approve_user.php, specifically for the ID parameter. Alternatively, use a properly sanitized input validation layer and ensure least-privilege database accounts.

Fix this in Online Tour \& Travel Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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