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

CVE-2025-67940

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 Mikado-Themes Powerlift powerlift allows PHP Local File Inclusion.This issue affects Powerlift: from n/a through < 3.2.1.

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 Powerlift theme by Mikado-Themes contains a Local File Inclusion (LFI) vulnerability where improper control of filenames in PHP include/require statements allows attackers to include arbitrary PHP files from the server. This stems from insufficient input validation on parameters used in file inclusion functions within the theme.

MitigationUpdate Powerlift theme to version 3.2.1 or later to obtain the vendor patch. If immediate update is not possible, implement strict input validation on all file inclusion parameters 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. Confirm Powerlift theme installation
    Locate the Powerlift theme directory in the WordPress themes folder (typically wp-content/themes/powerlift/) and find the style.css file which contains the theme version in the comment header
    Affected if The Powerlift theme directory exists and contains a style.css file with version information
  2. Identify installed theme version
    Open the style.css file in the Powerlift theme directory and read the Version: field from the theme header comments
    Affected if The version number is below 3.2.1 or the Version field is missing entirely
  3. Find file inclusion code patterns
    Search PHP files within the Powerlift theme for include, include_once, require, or require_once statements that use variables from $_GET, $_POST, $_REQUEST, or similar superglobals without sanitization
    Affected if The theme contains PHP include/require statements that directly incorporate user-supplied parameters without validation
  4. Check for vulnerable parameter usage
    Examine the identified include/require statements to determine if the parameter controlling the file path comes directly from user input without path traversal protection or whitelist validation
    Affected if File inclusion functions use raw user input from request parameters as the file path
  5. Test for LFI via HTTP requests
    Send HTTP requests to the WordPress site with path traversal sequences in parameters that may control file inclusion (e.g., ../../../../etc/passwd or ../../wp-config.php) and observe if file contents are returned
    Affected if The server returns contents of files outside the theme directory based on user-controlled parameters in the request

If the Powerlift theme version is below 3.2.1 and contains PHP include/require statements that use unsanitized user input for file paths, the environment is affected by CVE-2025-67940

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 Powerlift theme to version 3.2.1 or later to obtain the vendor patch. If immediate update is not possible, implement strict input validation on all file inclusion parameters and disable allow_url_include in PHP configuration.

Recommended fix Moderate confidence

Powerlift 3.2.1 or later

  1. 1. Backup your current Powerlift theme files and database
  2. 2. Obtain the fixed version of Powerlift (version 3.2.1 or later) from the official Mikado-Themes source
  3. 3. Replace the existing Powerlift theme files with the updated version
  4. 4. Verify that the new version is installed correctly by checking the theme version in WordPress admin
  5. 5. Test the site functionality to ensure the update did not break existing features
  6. 6. Clear any caching systems (server-side cache, CDN, plugin caches) after the update
Caveat Review theme customizations and child theme compatibility after upgrading to ensure custom code works with the new version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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