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

CVE-2025-25174

CRITICAL · 10.0 CVSS v3.1 Published 2025-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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 beeteam368 BeeTeam368 Extensions beeteam368-extensions allows PHP Local File Inclusion.This issue affects BeeTeam368 Extensions: from n/a through <= 1.9.4.

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

A PHP Local File Inclusion (LFI) vulnerability in the beeteam368-extensions WordPress plugin (versions up to 1.9.4) allows attackers to include arbitrary PHP files from the local filesystem via improper validation of include/require statement parameters, potentially leading to remote code execution.

MitigationUpdate to the latest patched version of beeteam368-extensions when available, or disable the plugin until a fix is released. Additionally, ensure PHP allow_url_include is disabled and web server configurations restrict file access.

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
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Locate the beeteam368-extensions plugin in WordPress
    Navigate to the wp-content/plugins/ directory and check for a folder named beeteam368-extensions or similar. In the WordPress admin dashboard, go to Plugins > Installed Plugins and look for beeteam368-extensions.
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed version of the plugin
    Open the main plugin PHP file (often found in the plugin root directory) or the readme.txt file within the plugin folder. Look for a version number declared in the plugin header or changelog.
    Affected if The installed version is 1.9.4 or any version prior to the patched release
  3. Verify the plugin is active
    In the WordPress admin dashboard under Plugins > Installed Plugins, check if beeteam368-extensions shows as 'Active' or 'Enabled'. Alternatively, check the wp_options table for the active_plugins option.
    Affected if The plugin is currently active on the WordPress site
  4. Check PHP configuration for allow_url_include
    Create a PHP file with the following content and access it via browser: <?php echo ini_get('allow_url_include'); ?> Or check the PHP configuration file (php.ini) directly.
    Affected if allow_url_include is set to On (this config does not directly prevent LFI but is a compounding risk factor)
  5. Assess web server file access restrictions
    Review the web server configuration (Apache .htaccess, Nginx config, or IIS web.config) for restrictions on file system access. Check if directories outside the web root are accessible.
    Affected if The web server configuration allows unrestricted file system access that could be exploited via the LFI vulnerability

A user is affected if the beeteam368-extensions plugin is installed, active, and running at version 1.9.4 or earlier, as the LFI vulnerability exists in these versions due to improper validation of include/require statement 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 to the latest patched version of beeteam368-extensions when available, or disable the plugin until a fix is released. Additionally, ensure PHP allow_url_include is disabled and web server configurations restrict file access.

Recommended fix Low confidence

Latest available version of beeteam368-extensions ( newer than 1.9.4 )

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'beeteam368-extensions' plugin
  4. 4. Check if an update is available and upgrade to the latest version
  5. 5. Verify the plugin was updated successfully after the upgrade completes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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