CVE-2025-9010
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. Affected by this vulnerability is an unknown functionality of the file /admin/booking_report.php. The manipulation of the argument from_date leads to sql injection. The attack can 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 confidenceA SQL injection vulnerability exists in the from_date parameter of /admin/booking_report.php in itsourcecode Online Tour and Travel Management System 1.0. An unauthenticated remote attacker can inject malicious SQL commands through this parameter to manipulate database queries, potentially allowing unauthorized data extraction, modification, or administrative operations on the underlying database.
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.
-
Identify the installed product versionLocate the application files and check for version indicators such as version files, about pages, or headers in the source code. Compare against version 1.0 of itsourcecode Online Tour and Travel Management System or Mayurik Online Tour & Travel Management System.Affected if The installed version is 1.0
-
Verify booking_report.php existsCheck if the file /admin/booking_report.php exists in the web root or application directory.Affected if The file /admin/booking_report.php is present in the application
-
Confirm unauthenticated access to admin panelAttempt to access /admin/booking_report.php directly via HTTP without providing any authentication credentials.Affected if The page is accessible without authentication
-
Inspect SQL query handling in booking_report.phpOpen /admin/booking_report.php in a text editor and locate the code handling the from_date parameter. Search for dynamic SQL construction (string concatenation or interpolation) used in database queries with this parameter.Affected if The from_date parameter is used in a SQL query without parameterized queries or input sanitization
A user is affected if they are running version 1.0 of itsourcecode/Mayurik Online Tour and Travel Management System with the /admin/booking_report.php file accessible and the from_date parameter handled via dynamic SQL queries.
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 parameterized queries (prepared statements) for all database operations involving the from_date parameter and audit other parameters in the application for similar SQL injection vulnerabilities. Restrict database user privileges and consider deploying a WAF as an additional security layer.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9010 — 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-9010 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