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

CVE-2025-8982

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. This vulnerability affects unknown code of the file /admin/operations/currency.php. The manipulation of the argument curr_code leads to sql injection. The attack can 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 · moderate confidence

SQL injection vulnerability in itsourcecode Online Tour and Travel Management System 1.0 allows remote attackers to inject malicious SQL queries via the curr_code parameter in /admin/operations/currency.php. The lack of input sanitization or parameterized queries enables unauthenticated attackers to manipulate database queries, potentially extracting sensitive data, modifying records, or gaining administrative access.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries in currency.php and implement strict input validation on the curr_code parameter. Apply principle of least privilege to 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 the installed version of the tour management system
    Check your web server for the application files. Look for version indicators in the source code, README files, or any version metadata. Compare against version 1.0.
    Affected if The installed version is 1.0 of Mayurik/itsourcecode Online Tour and Travel Management System
  2. Locate the vulnerable currency.php file
    Navigate to the /admin/operations/ directory in your web root and verify the presence of currency.php.
    Affected if The file /admin/operations/currency.php exists in the application installation directory
  3. Check if admin interface is accessible
    Attempt to access the /admin/ directory or /admin/operations/currency.php via HTTP request to determine if the admin panel is exposed.
    Affected if The admin panel at /admin/operations/currency.php is reachable over the network
  4. Inspect the curr_code parameter handling in currency.php
    Open currency.php and examine how the curr_code parameter is used in SQL queries. Look for direct concatenation of the parameter into SQL statements without prepared statements or input sanitization.
    Affected if The curr_code parameter is directly inserted into SQL queries without parameterized queries, prepared statements, or input validation/sanitization
  5. Verify database query patterns in currency.php
    Review the PHP source code for SQL queries containing 'curr_code' - check if the value is wrapped in quotes and concatenated directly into the query string rather than bound as a parameter.
    Affected if SQL queries involving curr_code use string concatenation or interpolation instead of binding the parameter

You are affected if the system is version 1.0, contains the /admin/operations/currency.php file, and the source code shows direct use of the curr_code parameter in SQL queries without prepared statements or sanitization.

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 prepared statements/parameterized queries in currency.php and implement strict input validation on the curr_code parameter. Apply principle of least privilege to database accounts.

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-8982 — 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-8982 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