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

CVE-2025-58214

HIGH · 8.1 CVSS v3.1 Published 2025-09-05
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 Indutri indutri allows PHP Local File Inclusion.This issue affects Indutri: from n/a through < 1.3.0.

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

A PHP Local File Inclusion (LFI) vulnerability exists in the gavias Indutri theme where user-supplied input is not properly validated before being used in include/require statements. This allows attackers to include arbitrary local PHP files, potentially achieving remote code execution if they can control the included files or leverage path traversal techniques.

MitigationUpgrade to Indutri version 1.3.0 or later. Additionally, implement strict input validation and whitelist-based filtering on any parameters used in include/require operations, avoiding direct use of user input in file path operations.

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 the installed Indutri theme version
    Locate the theme's main configuration file (typically version.php, theme.info.yml, or style.css in the theme directory) and check the version number declared there
    Affected if The version is below 1.3.0 (the patched version)
  2. Find PHP files using include/require with dynamic input
    Search the theme's PHP files for patterns like 'include($_' or 'require($_' or similar constructs where user-supplied superglobals are used directly in file inclusion functions
    Affected if Any include/require statement uses unsanitized $_GET, $_POST, $_REQUEST, or similar user input as the file path
  3. Inspect parameters used in file inclusion operations
    Examine the identified include/require calls to determine which URL parameters control the included file path; check if these parameters accept arbitrary file paths or can be manipulated with path traversal sequences like '../'
    Affected if The parameter allows path traversal or arbitrary file selection without validation
  4. Verify input validation exists on inclusion parameters
    Review the code around the include/require statements to see if there is any input validation, whitelist checking, or sanitization applied to the user-supplied parameter before it is used in the include/require function
    Affected if No validation or sanitization is performed on the parameter before it is used in include/require
  5. Test for path traversal vulnerability (if authorized)
    If you have a test environment, attempt to include a known local PHP file (e.g., the theme's own index.php or a standard system file) using a parameter like '?param=../index.php' or similar
    Affected if The application successfully includes files outside the intended directory

You are affected if the Indutri theme version is below 1.3.0 AND the theme contains PHP files that use user-supplied input directly in include/require statements without validation.

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

Upgrade to Indutri version 1.3.0 or later. Additionally, implement strict input validation and whitelist-based filtering on any parameters used in include/require operations, avoiding direct use of user input in file path operations.

Recommended fix Moderate confidence

1.3.0 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Appearance > Themes
  3. 3. Locate the gavias Indutri theme
  4. 4. Check if an update to version 1.3.0 or later is available
  5. 5. If available, update the theme to version 1.3.0 or latest version
  6. 6. Verify the update was successful and the site functions correctly

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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