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

CVE-2025-58215

HIGH · 8.1 CVSS v3.1 Published 2025-09-09
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 Ziston ziston allows PHP Local File Inclusion.This issue affects Ziston: from n/a through < 1.4.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 · moderate confidence

This is a PHP Local File Inclusion (LFI) vulnerability in the gavias Ziston theme that allows unauthenticated attackers to include arbitrary local files via improper control of filename parameters in include/require statements. The vulnerability stems from insufficient input validation on file path parameters, potentially enabling remote code execution.

MitigationUpgrade to Ziston version 1.4.5 or later which contains the security patch, or implement strict whitelist-based input validation on all file inclusion parameters to prevent path traversal.

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. Confirm gavias Ziston theme is installed
    Inspect your web application's wp-content/themes or themes directory for a folder named 'ziston', 'gavias-ziston', or similar. Check the style.css or theme.json file within that folder for the theme name and version declaration.
    Affected if The gavias Ziston theme is present in the themes directory and the version is below 1.4.5 or the version cannot be determined.
  2. Identify the installed Ziston version
    Open the theme's main style.css file (typically at wp-content/themes/ziston/style.css) and locate the 'Version:' header in the CSS comment block at the top. Alternatively, check theme.json for a 'version' field.
    Affected if The reported version is less than 1.4.5, or no version is declared.
  3. Locate PHP files handling file inclusion
    Search the theme directory for PHP files containing include, include_once, require, or require_once statements. Look for patterns like 'include($_GET[' or 'require($' that accept parameters without sanitization.
    Affected if File inclusion functions in the theme accept unsanitized user-supplied input from GET or POST parameters.
  4. Identify vulnerable file path parameters
    Review the PHP files found in the previous step for parameter names that suggest file paths, such as 'file', 'path', 'page', 'template', 'view', or 'action'. Test whether these parameters accept path traversal sequences like '../' or absolute paths.
    Affected if The application allows reading arbitrary files from the server through path traversal or direct file path input in file inclusion functions.

Your environment is affected if the gavias Ziston theme is installed with a version prior to 1.4.5 and exposes file inclusion functionality that accepts unsanitized user input.

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 Ziston version 1.4.5 or later which contains the security patch, or implement strict whitelist-based input validation on all file inclusion parameters to prevent path traversal.

Recommended fix Moderate confidence

Ziston version 1.4.5 or latest stable release

  1. 1. Backup your entire website (files and database) before performing any upgrade.
  2. 2. Identify your current Ziston theme version (typically found in theme style.css or version.php file).
  3. 3. Download Ziston version 1.4.5 or the latest stable version from the official gavias theme provider.
  4. 4. Replace the existing Ziston theme files with the new version, preserving any custom child theme or custom configuration if applicable.
  5. 5. Clear any application caches (PHP opcache, framework caches).
  6. 6. Verify the website functionality and the vulnerability is resolved.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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