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

CVE-2025-67957

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 TangibleWP Listivo Core listivo-core allows PHP Local File Inclusion.This issue affects Listivo Core: from n/a through <= 2.3.77.

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 in TangibleWP Listivo Core (versions <= 2.3.77) allows remote attackers to control filenames used in include/require statements, potentially enabling arbitrary PHP code execution if they can influence which files get included.

MitigationUpdate Listivo Core to version 2.3.78 or later; if no patch is available, disable the plugin and implement WAF rules to block suspicious include/require request patterns.

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 Listivo Core installation
    In WordPress admin dashboard, go to Appearance > Themes (if Listivo is a theme) or Plugins (if it's a plugin). Verify that Listivo Core is listed as active. Note the exact name displayed.
    Affected if Listivo Core theme or plugin is installed and active
  2. Identify installed version
    If Listivo is a theme, check the style.css file in wp-content/themes/listivo-core/ for the 'Version:' header. If it's a plugin, check the main plugin file header in wp-content/plugins/listivo-core/ for the 'Version:' comment.
    Affected if Version is 2.3.77 or lower (any version up to and including 2.3.77)
  3. Locate file inclusion code
    Search the Listivo Core theme/plugin directory for dynamic file inclusion functions: grep -r 'include' --include='*.php' and grep -r 'require' --include='*.php' combined with variable parameters (e.g., include($_, include($file, require_once($_GET[. Look for patterns where user input flows into include/require statements.
    Affected if File inclusion code exists that uses unvalidated user-supplied path parameters
  4. Check for vulnerable endpoints
    Review all PHP files that handle file path parameters from request input (GET, POST, REQUEST). Look for parameters that accept file paths and are used in include/require statements without proper sanitization. Common parameter names include 'file', 'path', 'template', 'page', 'slug'.
    Affected if Any file path parameter from user input is used directly in include/require without validation
  5. Inspect web server access logs
    Review web server access logs (apache2 access.log, nginx access.log) for suspicious requests targeting Listivo Core files with unusual path parameters. Look for patterns like ?file=../../ or ?path=/etc/passwd or other directory traversal attempts.

You are affected if Listivo Core version is 2.3.77 or lower AND the theme/plugin contains file inclusion functionality that uses unvalidated user-controlled path 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

Update Listivo Core to version 2.3.78 or later; if no patch is available, disable the plugin and implement WAF rules to block suspicious include/require request patterns.

Recommended fix Moderate confidence

Upgrade to any Listivo Core version higher than 2.3.77 (check TangibleWP for the latest stable release)

  1. 1. Identify the current installed version of Listivo Core plugin/theme in your WordPress installation.
  2. 2. Navigate to your WordPress admin dashboard, then go to Plugins or Theme settings to check the version number.
  3. 3. If the installed version is 2.3.77 or lower, this vulnerability is present.
  4. 4. Check the official TangibleWP source (tangiblewp.com or the WordPress repository) for the latest available version of Listivo Core.
  5. 5. Before upgrading, backup your entire WordPress installation including database and files.
  6. 6. Test the upgrade in a staging environment first if possible.
  7. 7. Upgrade to the latest available version of Listivo Core (version higher than 2.3.77).
  8. 8. Verify the upgrade was successful by confirming the new version number.
Caveat Minor or major version upgrades may introduce template/setting changes; test in staging before production deployment

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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