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

CVE-2025-59550

HIGH · 8.1 CVSS v3.1 Published 2025-10-22
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 designervily Xcare xcare allows PHP Local File Inclusion.This issue affects Xcare: from n/a through < 6.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 · high confidence

This is a PHP Remote File Inclusion vulnerability in the designervily Xcare application. The vulnerability allows attackers to include malicious PHP files through user-controlled input in include/require statements without proper validation, potentially leading to remote code execution. The issue affects versions prior to 6.5.

MitigationImplement strict input validation and sanitization for all file inclusion parameters, use allowlists for permitted files, and avoid using user input directly in include/require statements.

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 designervily Xcare installation
    Search the web server document root for files or directories named 'xcare', 'designervily', or check application footer/header for the product name
    Affected if The designervily Xcare application is present on the server
  2. Determine installed version
    Check version.php, version.txt, or the application's admin panel for the version number. Compare it to the affected range (versions prior to 6.5)
    Affected if The installed version is below 6.5
  3. Locate file inclusion code
    Search source files for include(), require(), include_once(), or require_once() statements that reference variables in the include/require path (e.g., include($_GET['page']) or require($file)
    Affected if The application uses dynamic file inclusion with user-controlled variables
  4. Check input validation on inclusion parameters
    Examine the code handling file inclusion parameters. Look for sanitize, validation, or allowlist logic applied to the variable before the include/require statement
    Affected if No input validation or allowlisting is implemented on file inclusion parameters
  5. Verify exposure to user input
    Confirm the file inclusion parameter can be controlled via HTTP request parameters (GET/POST) without authentication barriers
    Affected if Unauthenticated users can control the file path used in include/require statements

The environment is affected if designervily Xcare versions prior to 6.5 are installed and the application contains dynamically-included files using unsanitized user input in include/require statements.

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 and sanitization for all file inclusion parameters, use allowlists for permitted files, and avoid using user input directly in include/require statements.

Recommended fix Moderate confidence

Xcare version 6.5 or later

  1. 1. Verify the exact version of designervily Xcare currently installed in your environment
  2. 2. Confirm the vulnerability exists in your version by reviewing the application's file inclusion mechanisms
  3. 3. Obtain version 6.5 or later of designervily Xcare from the official vendor
  4. 4. Before deploying, test the upgrade in a non-production environment to ensure compatibility
  5. 5. Create a full backup of the current installation including database and configuration files
  6. 6. Deploy the upgraded version 6.5 or later
  7. 7. Verify the file inclusion vulnerability is remediated by testing the previously vulnerable code paths
  8. 8. Monitor application logs for any errors after the upgrade
Caveat Review release notes for version 6.5 to check for any breaking changes or deprecations that may affect your implementation

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

Have this fixed 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-59550 — 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-59550 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