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

CVE-2026-25380

HIGH · 8.1 CVSS v3.1 Published 2026-03-25
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 jwsthemes Feedy feedy allows PHP Local File Inclusion.This issue affects Feedy: from n/a through < 2.1.5.

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

PHP Local File Inclusion (LFI) vulnerability in jwsthemes Feedy allows attackers to manipulate filename parameters in include/require statements to execute arbitrary PHP code from local files, potentially leading to full system compromise.

MitigationUpgrade to Feedy version 2.1.5 or later to obtain the patched code that properly validates and sanitizes file inclusion 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. Identify if Feedy theme is installed
    Check your WordPress installation's wp-content/themes or wp-content/plugins directory for a 'feedy' folder. In WordPress admin, go to Appearance > Themes to see if Feedy is active.
    Affected if The Feedy theme or plugin folder exists in the WordPress installation
  2. Determine installed Feedy version
    Check the style.css file in the Feedy theme folder for the 'Version:' header, or check the plugin main file if it's a plugin. This file is typically at /wp-content/themes/feedy/style.css or /wp-content/plugins/feedy/feedy.php
    Affected if Version is found to be below 2.1.5
  3. Locate vulnerable include/require statements
    Search the Feedy source code for include(), require(), include_once(), or require_once() statements that use variables in the filename parameter without sanitization. Look for patterns like include($filename) or require($_GET['file']) within Feedy's PHP files.
    Affected if File inclusion code exists that uses unsanitized user input in the path parameter
  4. Check if file inclusion is reachable
    Examine the PHP files containing vulnerable include/require statements to determine if they are directly accessible via web requests (not protected by authentication or include guards).
    Affected if The vulnerable files can be accessed directly without authentication

If Feedy version is below 2.1.5 and contains file inclusion code that uses unsanitized input in include/require statements, 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Feedy version 2.1.5 or later to obtain the patched code that properly validates and sanitizes file inclusion paths.

Recommended fix Moderate confidence

Feedy version 2.1.5 or later

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins.
  3. 3. Locate the 'Feedy' (jwsthemes Feedy) plugin in the list.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 2.1.5 or later.
  5. 5. Alternatively, download version 2.1.5 or the latest version from the official WordPress plugin repository or jwsthemes.
  6. 6. Deactivate the existing Feedy plugin, then delete it, and reinstall the updated version.
  7. 7. After updating, verify the plugin is functioning correctly and test the feed display functionality.
  8. 8. Confirm the vulnerability is remediated by ensuring the include/require statements properly validate file paths and do not allow arbitrary file inclusion.

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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