CVE-2025-8966
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 · uneditedA vulnerability was found in itsourcecode Online Tour and Travel Management System 1.0. This issue affects some unknown processing of the file /admin/operations/tax.php. The manipulation of the argument tname 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 · moderate confidenceA SQL injection vulnerability exists in the itsourcecode Online Tour and Travel Management System 1.0 within the /admin/operations/tax.php file. The tname parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries. This critical flaw (CVSS 9.8) can lead to unauthorized database access, data exfiltration, and potentially remote code execution.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the application is installedIdentify whether the itsourcecode Online Tour and Travel Management System or Mayurik Online Tour and Travel Management System is present on the server by searching for application files, checking web root directories, or reviewing installed web applicationsAffected if The application is present and matches the product name
-
Verify the version numberLocate version information within the application files, such as in README files, about pages, configuration files, or the main index page headerAffected if The installed version is 1.0
-
Locate the vulnerable PHP fileCheck whether the file tax.php exists in the /admin/operations/ directory within the web application rootAffected if The file tax.php exists at /admin/operations/tax.php in the web directory
-
Confirm admin interface accessibilityDetermine if the /admin/ directory and operations/tax.php are accessible over the network by attempting to access the URL path or reviewing web server access logsAffected if The /admin/operations/tax.php endpoint is accessible from the network
-
Check for the vulnerable parameterReview the tax.php source code to confirm it accepts a tname parameter in GET or POST requests and uses it in SQL queries without proper sanitizationAffected if The tname parameter is processed by tax.php and used in SQL queries without parameterized queries
A user is affected if they have itsourcecode/Mayurik Online Tour and Travel Management System version 1.0 installed with the tax.php file accessible at /admin/operations/tax.php and the application accepts the tname parameter in SQL queries without sanitization.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement prepared statements/parameterized queries for all database operations in tax.php and validate/sanitize all user inputs before using them in SQL queries. Additionally, apply the principle of least privilege to database accounts.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8966 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-8966 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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