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

CVE-2025-69037

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 Pippo pippo allows PHP Local File Inclusion.This issue affects Pippo: from n/a through <= 1.2.3.

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 · high confidence

This is a Local File Inclusion (LFI) vulnerability in the goalthemes Pippo theme where improper control of filenames in PHP include/require statements allows attackers to include arbitrary local PHP files by manipulating input parameters.

MitigationImplement strict input validation and whitelist-based file inclusion, avoiding direct use of user-supplied data in include/require statements; also consider disabling allow_url_include and reviewing all include/require paths.

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 Pippo theme installation
    Search the web server document root for directories or files named 'pippo', 'theme-pippo', or containing 'pippo' in the path. Common locations include /wp-content/themes/, /themes/, or similar web application theme directories.
    Affected if Pippo theme files are found on the server
  2. Identify Pippo theme version
    Check for a style.css, theme.json, or composer.json file within the Pippo theme directory. Look for a 'Version:' header in style.css or a 'version' field in JSON configuration files.
    Affected if The installed version is unknown or falls within an affected version range (check against official Pippo theme release notes)
  3. Find file inclusion statements
    Search the Pippo theme PHP files for include, require, include_once, or require_once statements. Use grep or similar: grep -r 'include\|require' /path/to/pippo/theme/ | grep -v '//'
    Affected if The theme contains include/require statements that incorporate user-controlled input
  4. Inspect file path parameters
    Examine the PHP files found in the previous step. Identify if any include/require statements use variables derived from $_GET, $_POST, $_REQUEST, or similar superglobals as the file path. Look for patterns like: include($_GET['file']); or require($theme_path . $_REQUEST['template']);
    Affected if File inclusion statements use unsanitized user input from request parameters as all or part of the file path
  5. Check PHP configuration
    Locate the php.ini or loaded PHP configuration. Verify the setting for allow_url_include. Check with: php -i | grep allow_url_include or inspect phpinfo() output.
    Affected if allow_url_include is enabled (set to On)
  6. Verify path traversal is possible
    Test (in a non-production environment) by attempting to include known system files via the vulnerable parameter, such as /etc/passwd or ../Configuration files. Observe if file contents are returned in the response.
    Affected if Arbitrary files can be read through the file inclusion mechanism

If the Pippo theme is installed and contains include/require statements that use unsanitized user input to control file paths, the environment is affected by this LFI vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and whitelist-based file inclusion, avoiding direct use of user-supplied data in include/require statements; also consider disabling allow_url_include and reviewing all include/require paths.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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