dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-67963

HIGH · 8.6 CVSS v3.1 Published 2026-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in ovatheme Movie Booking movie-booking allows Path Traversal.This issue affects Movie Booking: from n/a through <= 1.1.5.

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

A path traversal vulnerability exists in the ovatheme Movie Booking WordPress theme (versions up to 1.1.5) that allows attackers to escape the intended directory restrictions and access sensitive files outside the web root by manipulating file path inputs with '../' sequences.

MitigationUpdate the Movie Booking theme to the latest version which should contain patched input validation, or implement strict whitelist-based file access controls and proper path sanitization that rejects directory traversal sequences.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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 Movie Booking theme is installed
    Check the WordPress themes directory (wp-content/themes/) for a folder named 'movie-booking', 'ova-theme-movie-booking', or similar. List all theme directories and look for the Movie Booking theme.
    Affected if The theme folder exists in the WordPress themes directory.
  2. Determine the installed theme version
    Open the theme's style.css file (typically at wp-content/themes/[theme-folder]/style.css) and locate the 'Version:' header in the CSS comment block at the top of the file.
    Affected if The version number displayed is 1.1.5 or lower, or if no version is declared but the theme is present.
  3. Locate file handling or include functionality
    Search the theme folder for PHP files that contain file inclusion functions such as 'include', 'require', 'file_get_contents', or 'readfile' combined with parameters that might accept user input (e.g., 'file', 'path', 'page', 'template', 'slug'). Use grep or manually inspect PHP files in the theme directory.
    Affected if The theme contains PHP code that uses file inclusion functions with variable inputs that could accept path parameters.
  4. Check for path traversal vulnerability in file operations
    Examine any identified file handling code for direct use of user-supplied parameters in file paths without sanitization. Look for patterns where '$_GET', '$_POST', or '$_REQUEST' variables are used in file operations without cleaning '../' sequences or using realpath() validation.
    Affected if The code accepts file path parameters and uses them in file operations without validating that the resolved path stays within an allowed directory.
  5. Verify vulnerable endpoint accessibility
    If file handling endpoints were found (e.g., frontend pages that accept file parameters), attempt to access a known file outside the theme directory using '../' sequences in the parameter (e.g., ?file=../../wp-config.php). Note: This is a verification test only, not an active exploit.
    Affected if The application returns file contents from outside the intended directory, confirming path traversal is possible.

A user is affected if the Movie Booking theme version is 1.1.5 or lower AND the theme contains file handling functionality accessible via web requests that does not properly sanitize '../' sequences in path parameters.

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

Update the Movie Booking theme to the latest version which should contain patched input validation, or implement strict whitelist-based file access controls and proper path sanitization that rejects directory traversal sequences.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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