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

CVE-2025-62054

HIGH · 7.5 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 →
81/100
Remediation priority · High
Remotely reachable 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 favethemes Houzez Theme - Functionality houzez-theme-functionality.This issue affects Houzez Theme - Functionality: from n/a through <= 4.1.8.

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 PHP Remote File Inclusion (RFI) vulnerability in the Houzez Theme functionality plugin. The vulnerability allows attackers to include remote files via improper control of filename parameters in PHP include/require statements, potentially enabling arbitrary code execution on the affected server.

MitigationUpdate to a patched version of the Houzez Theme - Functionality plugin when available. Until then, disable the vulnerable component, implement WAF rules to block malicious include requests, and audit the codebase for insecure file inclusion patterns.

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

CVSS:3.1/AV:N/AC:H/PR:L/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 Houzez Theme functionality plugin is installed
    Check your WordPress plugins directory or theme files for the Houzez Theme and its functionality plugin component. Look for files named 'functionality.php' or similar within the Houzez theme directory.
    Affected if The Houzez Theme with its functionality plugin is present on the WordPress installation
  2. Locate the plugin version
    Check the plugin header comment in the main functionality plugin file (often found in includes/functions/ or similar within the Houzez theme folder) for the Version field, or check the WordPress plugins admin page for the installed version.
    Affected if The installed version matches or falls within the affected version range (if known) or is an unpatched version
  3. Identify the vulnerable file inclusion code
    Search the Houzez theme codebase for PHP include/require statements that use dynamic variables or parameters without proper sanitization. Look for patterns like 'include($_GET[...]' or 'require($' within the functionality plugin files.
    Affected if Insecure include/require patterns with unsanitized parameters exist in the functionality plugin files
  4. Check if the vulnerable endpoint is accessible
    Attempt to access any publicly exposed PHP files in the functionality plugin that handle file inclusion parameters. Review the plugin's AJAX handlers or frontend-facing PHP files that may process filename parameters.
    Affected if The vulnerable file inclusion code can be reached via HTTP requests without authentication

Your environment is affected if the Houzez Theme functionality plugin is installed, contains insecure include/require statements with unsanitized parameters, and those endpoints are accessible without proper access controls.

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

Update to a patched version of the Houzez Theme - Functionality plugin when available. Until then, disable the vulnerable component, implement WAF rules to block malicious include requests, and audit the codebase for insecure file inclusion patterns.

Recommended fix Moderate confidence

Latest available version of Houzez Theme - Functionality (version > 4.1.8)

  1. Identify the current version of Houzez Theme - Functionality plugin installed on the WordPress site
  2. Access the WordPress admin dashboard or check the plugin version through file inspection
  3. Navigate to Plugins > Installed Plugins > Houzez Theme - Functionality
  4. If an update is available, click 'Update Now' to upgrade to the latest patched version
  5. Verify the update completed successfully and the plugin is running on a version higher than 4.1.8
  6. Test critical site functionality to ensure the update did not break existing features
Caveat Minor or major compatibility issues possible if theme or other plugins have dependencies on specific Houzez functionality versions

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