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

CVE-2025-67988

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 CozyStay cozystay allows PHP Local File Inclusion.This issue affects CozyStay: from n/a through < 1.9.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

This is a Local File Inclusion (LFI) vulnerability in the CozyStay PHP application where improper control of filename parameters in include/require statements allows attackers to include arbitrary local PHP files. This can lead to sensitive file disclosure (configuration files, source code) and potentially remote code execution depending on server configuration.

MitigationUpgrade to CozyStay version 1.9.1 or later. If no patch is available, implement strict whitelist-based input validation on all file inclusion parameters, disable allow_url_include, and use basename() with realpath() to prevent path traversal attacks.

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. Identify CozyStay installation
    Locate CozyStay PHP files on the server by searching for common CozyStay file paths (e.g., index.php, admin/, includes/ directories with CozyStay branding). Check web root for CozyStay-specific directories.
    Affected if CozyStay PHP application is present on the server
  2. Check CozyStay version
    Locate the version file or check the header/metadata of core CozyStay PHP files for the version number. Compare against the fixed version 1.9.1.
    Affected if Installed version is lower than 1.9.1
  3. Identify file inclusion endpoints
    Search the CozyStay source code for include, require, include_once, or require_once statements that accept user-controlled parameters (e.g., using $_GET, $_POST, or $_REQUEST as the filename).
    Affected if The application contains include/require statements using unsanitized input from request parameters
  4. Test for LFI vulnerability
    If file inclusion endpoints exist, attempt a safe test by passing a benign local file path (e.g., ../../index.php or /etc/passwd equivalent on Windows) as a parameter to see if the file contents are returned.
    Affected if The application returns contents of arbitrary local files when path traversal sequences are provided in the parameter
  5. Check PHP configuration
    Examine the PHP configuration file (php.ini) for the allow_url_include setting. If enabled, this could allow remote file inclusion in addition to local file inclusion.
    Affected if allow_url_include is enabled in php.ini (this worsens the impact but the LFI exists regardless)
  6. Review included file paths
    Inspect the specific PHP files handling include/require to verify whether they use basename(), realpath(), or other sanitization functions on the input before the include statement.
    Affected if File inclusion code lacks proper path sanitization using basename() or realpath()

The environment is affected if CozyStay version is below 1.9.1 AND the application contains file inclusion logic that uses unsanitized request parameters, allowing path traversal to read arbitrary local files.

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 CozyStay version 1.9.1 or later. If no patch is available, implement strict whitelist-based input validation on all file inclusion parameters, disable allow_url_include, and use basename() with realpath() to prevent path traversal attacks.

Recommended fix Moderate confidence

Upgrade to CozyStay version 1.9.1 or later

  1. Identify the current version of the LoftOcean CozyStay (cozystay) installation
  2. Navigate to the official vendor source or WordPress plugin repository for CozyStay
  3. Download and apply version 1.9.1 or the latest stable release available
  4. Verify the upgrade was successful by checking the plugin/theme version number
  5. Test the application to ensure normal functionality is maintained
Caveat Review release notes for any breaking changes between your current version and 1.9.1; test in a staging environment before deploying to production

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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