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

CVE-2025-27362

HIGH · 8.1 CVSS v3.1 Published 2025-06-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 BZOTheme Petito bw-petito allows PHP Local File Inclusion.This issue affects Petito: from n/a through < 1.6.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

A Local File Inclusion (LFI) vulnerability exists in BZOTheme Petito (bw-petito) versions before 1.6.6. The application improperly validates file path inputs in include/require statements, allowing attackers to manipulate filename parameters to include arbitrary PHP files from the local system, potentially leading to remote code execution.

MitigationUpgrade Petito to version 1.6.6 or later. If no patch is available, implement strict input validation on all file inclusion parameters using allowlists and disable allow_url_include in PHP configuration.

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 Petito theme installation
    Locate the theme directory in your web application's web root. Look for a folder named 'petito' or 'bw-petito' typically under /themes/ or /template/. Check for style.css containing 'Petito' or 'bw-petito' in the theme metadata header.
    Affected if The Petito theme is installed on the server
  2. Determine installed version
    Open the theme's version.php, header.php, or style.css file and locate the version number. Compare it to the affected range: versions before 1.6.6 are vulnerable.
    Affected if Installed version is below 1.6.6
  3. Locate file inclusion code
    Search PHP files in the theme directory for dynamic include/require statements. Look for patterns like include($var), require($_GET['file']), or similar where user-supplied parameters are used directly in file paths.
    Affected if File inclusion code uses unsanitized parameters from HTTP requests
  4. Check for vulnerable parameter exposure
    Identify which GET/POST parameters control the file inclusion (common names include 'page', 'file', 'template', 'path', 'load'). Verify if these parameters accept relative or absolute file paths without sanitization.
    Affected if File inclusion parameters accept arbitrary file paths without validation

The environment is affected if Petito (bw-petito) theme version is below 1.6.6 and the application contains file inclusion code that uses unsanitized user input from HTTP request parameters.

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 Petito to version 1.6.6 or later. If no patch is available, implement strict input validation on all file inclusion parameters using allowlists and disable allow_url_include in PHP configuration.

Recommended fix Moderate confidence

BZOTheme Petito version 1.6.6 or later

  1. 1. Identify all deployments of the BZOTheme Petito (bw-petito) theme in your environment
  2. 2. Check the current installed version of the Petito theme
  3. 3. Create a full backup of the current theme files and database
  4. 4. Download the latest version of Petito (version 1.6.6 or higher) from the official theme provider
  5. 5. Replace the existing theme files with the new version
  6. 6. Clear any application caches
  7. 7. Verify the vulnerability is resolved by testing that arbitrary file inclusion is no longer possible
  8. 8. Test that normal theme functionality remains intact after the upgrade

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