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

CVE-2025-60199

HIGH · 8.1 CVSS v3.1 Published 2025-11-06
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 dedalx InHype - Blog & Magazine WordPress Theme inhype allows PHP Local File Inclusion.This issue affects InHype - Blog & Magazine WordPress Theme: from n/a through <= 1.5.2.

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

Local File Inclusion vulnerability in the InHype WordPress theme allows attackers to include arbitrary PHP files from the server through improper control of filename parameters in include/require statements, potentially enabling remote code execution.

MitigationUpdate to a patched version of the InHype theme when available; alternatively, audit and secure all include/require statements in the theme to enforce strict input validation and whitelist-based file access controls.

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 if InHype theme is installed
    Check the WordPress themes directory (wp-content/themes/) for a folder named 'inhype' or similar. Alternatively, access WordPress admin dashboard and navigate to Appearance > Themes to see the list of installed themes.
    Affected if The InHype theme folder exists in wp-content/themes/ or the theme appears in WordPress admin theme list
  2. Determine the InHype theme version
    Check the style.css file within the InHype theme folder for a 'Version:' header, or look for a version constant in the theme's main PHP file. In WordPress admin, go to Appearance > Themes and click on InHype to view its details.
    Affected if The version displayed is within or below any known vulnerable version range for this CVE
  3. Locate include/require statements in theme files
    Search the InHype theme folder for PHP files containing include, include_once, require, or require_once statements that use variables in the file path (e.g., include($file), require($_GET['param']). Use grep or a file search tool: grep -r "include(\|require(\|include_once(\|require_once(" --include="*.php" /path/to/wp-content/themes/inhype/
    Affected if Any include/require statements use unsanitized user input or variable file paths without validation
  4. Check for file parameter handling in PHP files
    Examine PHP files that handle file parameters, particularly in controllers, template files, or ajax handlers. Look for patterns like $_GET['file'], $_POST['file'], or any request parameters used in file inclusion functions.
    Affected if File-related parameters from GET/POST requests are used directly in include/require without validation or whitelist filtering
  5. Inspect the specific vulnerable code location
    If known, examine the specific file(s) reported as vulnerable in this CVE. Review the file path construction logic around any include/require statements for improper input validation.
    Affected if The vulnerable code pattern exists and accepts user-controlled input for file inclusion

You are affected if the InHype theme is installed and contains include/require statements that use unsanitized user input or variable file paths, allowing arbitrary PHP file inclusion.

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 to a patched version of the InHype theme when available; alternatively, audit and secure all include/require statements in the theme to enforce strict input validation and whitelist-based file access controls.

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-60199 — 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-60199 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