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

CVE-2025-31064

HIGH · 8.1 CVSS v3.1 Published 2025-05-23
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 gavias Vizeon - Business Consulting vizeon allows PHP Local File Inclusion.This issue affects Vizeon - Business Consulting: from n/a through < 1.2.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 PHP Local File Inclusion (LFI) vulnerability in the Vizeon - Business Consulting theme. The application improperly validates or controls filenames used in PHP include/require statements, allowing attackers to potentially read sensitive local files from the server filesystem by manipulating the file path parameters.

MitigationImplement strict input validation and whitelist-based filtering for any user-controlled parameters used in include/require statements. Additionally, disable allow_url_include in PHP configuration and consider using a whitelist of allowed files rather than direct path inclusion.

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. Locate the Vizeon theme installation
    Search for files or directories containing 'vizeon' in the web root, typically found in wp-content/themes/vizeon for WordPress installations or similar theme directories for other platforms
    Affected if The Vizeon theme directory exists on the server
  2. Identify the installed theme version
    Check for a style.css, theme.json, or version.php file within the Vizeon theme directory that contains a version declaration; compare the version number against any known affected ranges
    Affected if The theme version cannot be determined or falls within an unknown/unspecified vulnerable range
  3. Find PHP include/require statements using dynamic paths
    Grep the theme directory for PHP include(), require(), include_once(), or require_once() statements where the path argument contains variables (e.g., include($var), include($_GET['param']), include($_POST['param']))
    Affected if Dynamic file inclusion patterns using unsanitized variables are present in the theme code
  4. Identify user-controlled parameters in file inclusions
    Examine the variables used in include/require statements to determine if they originate from $_GET, $_POST, $_REQUEST, or other user-supplied input without proper validation
    Affected if File inclusion paths are constructed from URL parameters or form inputs without validation
  5. Verify lack of input validation on file path parameters
    Review the code handling the file path parameters to check for functions like basename(), realpath(), or whitelist validation; look for any filter or validation logic before the include/require statement
    Affected if No input validation, sanitization, or whitelist filtering is applied to file path parameters before inclusion
  6. Test for LFI vulnerability exploitation
    If vulnerable code is identified, attempt to include a known local file such as /etc/passwd or ../../config.php through the suspected parameter to confirm the LFI exists
    Affected if The application returns contents of local files when path parameters are manipulated

A user is affected if the Vizeon theme is installed, contains PHP include/require statements using user-controlled variables without validation, and lacks input sanitization on file path parameters.

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 whitelist-based filtering for any user-controlled parameters used in include/require statements. Additionally, disable allow_url_include in PHP configuration and consider using a whitelist of allowed files rather than direct path inclusion.

Recommended fix Moderate confidence

1.2.1 or latest available release

  1. 1. Identify the current version of the gavias Vizeon - Business Consulting theme/plugin installed on your system
  2. 2. If the current version is below 1.2.1, backup your website files and database before proceeding
  3. 3. Download the updated version 1.2.1 or the latest stable release from the official gavias theme provider
  4. 4. Install the updated version following the vendor's standard upgrade procedure
  5. 5. Verify that the LFI vulnerability has been addressed by reviewing the patched code (check for proper input validation on include/require statements)
  6. 6. Test the application to ensure normal functionality is maintained after the update

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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