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

CVE-2025-49508

HIGH · 8.1 CVSS v3.1 Published 2025-06-17
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.7.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 · high confidence

A PHP Local File Inclusion (LFI) vulnerability exists in CozyStay where user-supplied input is used in include/require statements without proper validation. This allows attackers to include arbitrary local PHP files, potentially leading to remote code execution if they can upload files or access sensitive system files.

MitigationImplement strict input validation using allowlists, avoid using user input directly in include/require statements, and upgrade to version 1.7.1 or later if a patch is available.

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 installed CozyStay version
    Check the version file or header in the CozyStay installation, typically found in a version.php file, composer.json, or admin dashboard about page
    Affected if The installed version is earlier than 1.7.1 or cannot be determined
  2. Locate PHP files using include/require with user input
    Search the codebase for patterns like 'include($_GET' or 'require($_POST' to identify where user input flows directly into file inclusion functions
    Affected if User-controlled parameters are used directly in include, require, include_once, or require_once statements without sanitization
  3. Identify vulnerable parameter sources
    Examine URL parameters (GET/POST) that control file inclusion paths, typically found in routing files or page templates
    Affected if Parameters like 'page', 'file', 'template', or 'path' are used to construct include/require paths without validation
  4. Check for file upload functionality
    Review if the application allows file uploads and where uploaded files are stored (usually in an accessible web directory)
    Affected if File upload exists and uploaded files are accessible via web, making RCE chaining possible
  5. Verify the version is below fixed release
    Compare the identified version against the fixed version 1.7.1 using the version check from step 1
    Affected if The installed version is below 1.7.1 and any of the vulnerable include/require patterns exist

A user is affected if running a CozyStay version below 1.7.1 with user input being used unsanitized in PHP include/require statements, especially if file upload functionality is present.

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

Implement strict input validation using allowlists, avoid using user input directly in include/require statements, and upgrade to version 1.7.1 or later if a patch is available.

Recommended fix High confidence

1.7.1 or later

  1. Backup your WordPress site and database before performing any updates
  2. Update the CozyStay plugin to version 1.7.1 or later through the WordPress admin dashboard (Plugins > Updates) or via wp-cli: wp plugin update cozystay
  3. Verify the update was successful by checking the plugin version in Plugins list
  4. 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-49508 — 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-49508 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