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

CVE-2025-32289

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 ApusTheme Yozi yozi allows PHP Local File Inclusion.This issue affects Yozi: from n/a through <= 2.0.63.

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 vulnerability exists in the ApusTheme Yozi theme where user-controlled input is used in include/require statements without proper validation, allowing attackers to potentially execute arbitrary PHP code by manipulating file paths.

MitigationUpdate to a patched version of the Yozi theme. If no patch is available, implement strict whitelist-based input validation on parameters used in include/require operations and review all file inclusion paths in the codebase.

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. Verify Yozi theme installation
    Search the web server document root for the Yozi theme directory - typically found under wp-content/themes/yozi/ (WordPress) or in the themes/ folder. Look for theme configuration files like style.css, functions.php, or theme initialization files.
    Affected if The Yozi theme directory exists on the server
  2. Determine Yozi theme version
    Open the theme's style.css file in the Yozi theme directory and locate the 'Version:' header in the CSS comment block at the top. Alternatively, check version.php or theme.json if present.
    Affected if The version number cannot be determined or is lower than the patched version
  3. Locate file inclusion functions in theme code
    Search all PHP files in the Yozi theme directory for dynamic include/require patterns: grep for 'include(', 'require(', 'include_once(', 'require_once(' where the path contains a variable (e.g., include($var), require($_GET['param'])).
    Affected if Dynamic file inclusion calls using variables are found in theme PHP files
  4. Identify user-controllable parameters
    Examine the dynamic include/require calls found and trace which parameters feed into them. Check if these parameters come from $_GET, $_POST, $_REQUEST, or other user-accessible sources.
    Affected if Parameters used in include/require statements are sourced from user input without sanitization
  5. Test parameter accessibility
    If vulnerable parameters are identified, attempt to manipulate them via URL query parameters (GET) or form submissions (POST) to see if arbitrary file paths can be included. For example, try including a known file like /etc/passwd or a non-PHP file.
    Affected if The file inclusion parameter can be manipulated to include arbitrary files from the server filesystem

If the Yozi theme is installed, uses dynamic file inclusion with user-supplied parameters, and those parameters are accessible without sanitization, the environment is vulnerable to CVE-2025-32289.

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 Yozi theme. If no patch is available, implement strict whitelist-based input validation on parameters used in include/require operations and review all file inclusion paths in the codebase.

Recommended fix Moderate confidence

Latest available Yozi theme version (check Themeforest for current version > 2.0.63)

  1. Check the Themeforest/ApusTheme official page for Yozi theme to identify the latest available version
  2. Review the theme's changelog or contact the theme developer to confirm which version includes the security fix for CVE-2025-32289
  3. Backup your current website before performing any updates
  4. Update the Yozi theme to the latest version available from the theme developer
  5. Verify the update was successful and test the site functionality
Caveat Review theme changelog for any breaking changes between your current version and the new version before upgrading

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