dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-67992

HIGH · 8.1 CVSS v3.1 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in LoftOcean PatioTime patiotime allows PHP Local File Inclusion.This issue affects PatioTime: from n/a through < 2.1.

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 PHP Local File Inclusion vulnerability in LoftOcean's PatioTime plugin allows attackers to include arbitrary local files via unsanitized input parameters in include/require statements, potentially exposing sensitive server files or enabling code execution.

MitigationUpgrade to PatioTime version 2.1 or later which contains the patch, or implement strict whitelist-based input validation and path sanitization on all file inclusion logic to prevent directory traversal.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Check if PatioTime plugin is installed
    Identify whether the LoftOcean PatioTime plugin is present in the PHP application. This may involve listing installed plugins, checking the plugin directory, or reviewing the application's plugin management interface.
    Affected if The PatioTime plugin is found installed or active in the environment
  2. Determine the installed version of PatioTime
    Locate the plugin's version information. This is typically found in the plugin's main PHP file header, a version constant, a composer.json file, or a dedicated version/configuration file within the plugin directory.
    Affected if The installed version cannot be determined or is found to be earlier than version 2.1
  3. Compare the version to the affected range
    Match the identified version against the affected range: any version of PatioTime prior to version 2.1 is considered vulnerable.
    Affected if The installed version is below 2.1 (for example, 2.0, 1.x, or earlier)
  4. Identify vulnerable file inclusion code
    Search the plugin source code for include, include_once, require, or require_once statements that use unsanitized user-supplied input (such as $_GET, $_POST, or $_REQUEST parameters) without proper path validation or directory traversal protection.
    Affected if File inclusion logic uses untrusted input without sanitization, allowing directory traversal sequences like ../
  5. Verify parameter accessibility
    Determine whether the vulnerable parameters are directly accessible via HTTP requests (GET/POST). Test if the affected include/require paths can be manipulated through URL parameters.
    Affected if The vulnerable file inclusion parameters are exposed and can be manipulated via HTTP requests

The environment is affected if the PatioTime plugin is installed with a version earlier than 2.1 and the vulnerable file inclusion code using unsanitized input is present and accessible.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to PatioTime version 2.1 or later which contains the patch, or implement strict whitelist-based input validation and path sanitization on all file inclusion logic to prevent directory traversal.

Recommended fix Moderate confidence

PatioTime version 2.1 or later

  1. 1. Back up the current PatioTime installation including all files and the database
  2. 2. Download PatioTime version 2.1 or later from the official LoftOcean source or repository
  3. 3. Extract the new version files
  4. 4. Replace the existing PatioTime files with the new version files, preserving any custom configuration if required
  5. 5. Clear any PHP opcode caches (e.g., OPcache, APCu) if enabled
  6. 6. Verify the application functions correctly after the upgrade
  7. 7. Test that the file inclusion vulnerability is no longer exploitable

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

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