dbcve.org
Online Traveling SystemApplication · Scriptandtools

CVE-2025-4064

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 ScriptAndTools Online-Travling-System 1.0. It has been classified as critical. This affects an unknown part of the file /admin/viewenquiry.php. The manipulation leads to improper access controls. 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 · moderate confidence

The vulnerability exists in the admin panel file /admin/viewenquiry.php of ScriptAndTools Online-Traveling-System 1.0. It allows unauthorized access due to improper access controls, likely missing authentication or authorization checks on this admin-only page. The CVSS 5.3 indicates a medium-severity access control bypass that can be exploited remotely.

MitigationImplement proper authentication and role-based authorization checks on all admin-panel pages, including viewenquiry.php, ensuring only authenticated administrators can access sensitive admin functions.

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 Traveling 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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. Confirm ScriptAndTools Online-Traveling-System installation
    Check if the application files exist on the web server. Look for directories containing 'travel', 'scriptandtools', or 'online-traveling' in the web root. The vulnerable component is typically installed at /admin/viewenquiry.php within this application.
    Affected if The ScriptAndTools Online-Traveling-System version 1.0 is installed on the server
  2. Verify the vulnerable file exists
    Check for the presence of /admin/viewenquiry.php in the application directory. On Linux, use: find /var/www -name 'viewenquiry.php' 2>/dev/null or locate the admin folder within the travel system web directory.
    Affected if The file /admin/viewenquiry.php exists in the web application
  3. Test unauthenticated access to the admin page
    Using curl or a browser, attempt to access http://[target]/admin/viewenquiry.php without providing any login credentials or session cookies. Check if the page loads and displays content instead of redirecting to a login page.
    Affected if The page loads and displays content or functionality without requiring authentication (returns HTTP 200 instead of 401/302 redirect to login)
  4. Inspect the source code for access control checks
    If file access is available, examine /admin/viewenquiry.php and look for PHP code that validates user authentication before processing requests. Search for patterns like 'session_start()', '$_SESSION', 'is_admin', or 'authenticate' near the top of the file.
    Affected if The file contains no session initialization, no authentication checks, or no role/privilege validation before executing sensitive operations
  5. Check admin directory access control configuration
    Examine the /admin/ directory for a common entry point or index file that might handle authentication. Verify if authentication is enforced at the directory level or if individual admin PHP files are expected to handle their own auth checks.
    Affected if No central authentication mechanism exists for the /admin/ directory, requiring each file to implement its own access controls

A defender is affected if ScriptAndTools Online-Traveling-System 1.0 is installed and the /admin/viewenquiry.php page is accessible without authentication, indicating missing access controls on that admin panel page.

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 proper authentication and role-based authorization checks on all admin-panel pages, including viewenquiry.php, ensuring only authenticated administrators can access sensitive admin functions.

Fix this in Online Traveling System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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