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

CVE-2025-69322

HIGH · 8.1 CVSS v3.1 Published 2026-02-20
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 fuelthemes PeakShops peakshops allows PHP Local File Inclusion.This issue affects PeakShops: from n/a through < 1.5.9.

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

The PeakShops theme by fuelthemes contains a PHP Local File Inclusion (LFI) vulnerability that allows attackers to include arbitrary PHP files from the server file system due to improper control of filenames in include/require statements. This can lead to remote code execution if attackers can control the included files.

MitigationUpgrade PeakShops to version 1.5.9 or later. As a compensating control, disable allow_url_include in php.ini and implement strict input validation on all file inclusion parameters.

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 PeakShops theme is installed
    Search the web server document root for PeakShops theme files. Look for a theme directory containing PHP files, configuration files, or version metadata associated with the PeakShops product.
    Affected if PeakShops PHP theme files exist in the environment
  2. Determine installed PeakShops version
    Locate the theme version file, composer.json, header comments in main PHP files, or any version identifier within the PeakShops theme directory. Compare this version to 1.5.9.
    Affected if Installed version is lower than 1.5.9
  3. Locate file inclusion code in PHP files
    Search all PHP files in the PeakShops theme directory for dynamic include(), require(), include_once(), or require_once() statements. Identify any that accept variables or request parameters without sanitization.
    Affected if Dynamic file inclusion using user-supplied input without validation is present
  4. Inspect web application parameters for file paths
    Review forms, URL parameters, or API endpoints that accept file or path parameters. Test whether these inputs can be manipulated to include arbitrary local files such as ../../etc/passwd or configuration files.
    Affected if File path parameters accept traversal sequences or arbitrary local file paths

The environment is affected if the installed PeakShops version is below 1.5.9 and the theme contains PHP include/require statements that process user input without validation.

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 PeakShops to version 1.5.9 or later. As a compensating control, disable allow_url_include in php.ini and implement strict input validation on all file inclusion parameters.

Recommended fix Moderate confidence

PeakShops version 1.5.9 or later

  1. 1. Backup the current website files and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard > Appearance > Themes
  3. 3. Locate the PeakShops theme and check the current version number
  4. 4. If an update to version 1.5.9 or later is available through the WordPress theme repository or fuelthemes distribution, update to the latest version
  5. 5. If no update is available through WordPress, manually upload and install PeakShops version 1.5.9 or later from the official fuelthemes source (themeforest.net or fuelthemes.net)
  6. 6. After upgrade, clear any caching mechanisms (plugin cache, server-side cache, CDN cache)
  7. 7. Verify the application functions correctly after the upgrade
Caveat Review theme customizations and child theme compatibility after upgrading to ensure custom changes still function properly

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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