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

CVE-2025-69038

HIGH · 8.1 CVSS v3.1 Published 2026-01-22
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 goalthemes Hyori hyori allows PHP Local File Inclusion.This issue affects Hyori: from n/a through <= 1.3.6.

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 (LFI) vulnerability in the Hyori theme allows attackers to control filenames used in PHP include/require statements, potentially enabling unauthorized file reads or remote code execution through malicious file inclusion.

MitigationUpdate to the latest patched version of Hyori theme; if unavailable, implement strict input validation on all file inclusion parameters and consider deploying a WAF rule to block directory traversal 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
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 Hyori theme installation
    Locate the Hyori theme directory in your web application (commonly in /wp-content/themes/hyori/ for WordPress or the themes folder of the respective CMS). Check for the presence of theme files such as style.css, functions.php, or theme configuration files.
    Affected if The Hyori theme directory exists in your webroot or CMS theme folder
  2. Determine installed theme version
    Open the style.css file or theme.json in the Hyori theme directory and locate the version declaration in the theme header comments.
    Affected if The version number found is lower than the patched version released for this CVE, or the version cannot be determined (indicating an unpatched installation)
  3. Identify PHP file inclusion usage
    Search the Hyori theme PHP files for include, require, include_once, or require_once statements. Use grep or a text search to find occurrences where these functions are used with variables in the file path.
    Affected if The theme contains PHP files that use dynamic file inclusion with variables that could be user-controlled
  4. Inspect file inclusion parameters
    Examine the identified include/require statements to determine whether the file path or filename is derived from request parameters (GET, POST, COOKIE) or other user-controllable sources.
    Affected if File inclusion paths incorporate parameters directly from user requests without apparent sanitization
  5. Check for input validation
    Review the code handling the file inclusion parameters to see if there is any input validation, whitelisting, or sanitization before the include/require statement executes.
    Affected if No validation mechanism exists on the file inclusion parameters, or validation can be bypassed

Your environment is affected if the Hyori theme is present and contains PHP file inclusion logic that processes user-supplied input without proper validation, allowing potential directory traversal.

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 the latest patched version of Hyori theme; if unavailable, implement strict input validation on all file inclusion parameters and consider deploying a WAF rule to block directory traversal patterns.

Recommended fix Moderate confidence

Latest available Hyori theme version (newer than 1.3.6)

  1. 1. Update the Hyori theme to the latest available version from goalthemes or your WordPress theme repository
  2. 2. Verify the update was successful by checking the theme version in WordPress admin under Appearance > Themes
  3. 3. Confirm the vulnerability is resolved by testing that arbitrary file inclusion is no longer possible via the affected parameter
  4. 4. If automatic updates are not enabled, enable them or regularly check for theme updates

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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