critical CVSS 10

CVE-2025-25174·PHP vulnerability

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.

Severity
critical
Software
PHP
Published
2025-08-14

How to fix this CVE

Remove or update the BeeTeam368 Extensions plugin immediately. If the plugin must remain, restrict file upload capabilities and implement WAF rules to block LFI patterns. Audit the WordPress installation for signs of compromise including web shells and backdoor files.

# Remove the plugin:
wp plugin deactivate beeteam368-extensions --path=/var/www/html
wp plugin delete beeteam368-extensions --path=/var/www/html
# Or update to patched version if available:
wp plugin update beeteam368-extensions --path=/var/www/html
# Scan for web shells:
find /var/www -name '*.php' -exec grep -l 'eval(\|base64_decode(\|system(' {} \;

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

GET /wp-content/plugins/beeteam368-extensions/includes/template.php?file=../../../wp-config.php HTTP/1.1

The attacker manipulates file path parameters to include arbitrary PHP files. By traversing to wp-config.php, they extract database credentials. By including uploaded files or log files with injected PHP code, they achieve code execution.

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch.

SecRule ARGS "@rx (?:\.\.[\/\\]){2,}" "id:20252517,phase:2,deny,status:403,msg:'CVE-2025-25174 LFI path traversal blocked',severity:CRITICAL,tag:'CVE-2025-25174'"

SecRule REQUEST_URI "beeteam368" "id:20252518,phase:1,chain"
SecRule ARGS "@rx (?:etc/passwd|wp-config|proc/self)" "deny,status:403,msg:'LFI targeting sensitive files via BeeTeam368'"

How to check if you are affected

  1. Check if BeeTeam368 Extensions is installed: wp plugin list --path=/var/www/html | grep beeteam368
  2. Check plugin version: cat /var/www/html/wp-content/plugins/beeteam368-extensions/readme.txt | grep 'Stable tag'
  3. Search access logs for LFI attempts: grep -E 'beeteam368.*\.\./' /var/log/apache2/access.log
  4. Scan for web shells: find /var/www -name '*.php' -exec grep -l 'eval(base64_decode' {} \;
  5. Check wp-config.php access time: stat /var/www/html/wp-config.php

Indicators of compromise

  • HTTP requests to beeteam368-extensions paths with ../ sequences
  • Access to wp-config.php via plugin file inclusion
  • New PHP files in wp-content/uploads/ or wp-content/plugins/
  • Unexpected database queries from the WordPress application
  • Outbound connections from the web server to unknown IPs

FAQ

What is the BeeTeam368 Extensions plugin?

It is a WordPress plugin that provides various theme extensions and functionality. It is not as widely known as major plugins but is used on sites running BeeTeam368 themes.

Why is this CVSS 10.0?

Maximum CVSS score because: network-accessible (AV:N), no complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and complete compromise of confidentiality, integrity, and availability (C:H/I:H/A:H) with scope change (S:C).

Can this be exploited without uploading files?

Yes. LFI can include existing files like wp-config.php (credential disclosure), /etc/passwd (user enumeration), or log files that contain attacker-injected PHP code (log poisoning for RCE).

How do I check if my site was compromised?

Search for web shells: find /var/www -name '*.php' -newer /var/www/html/wp-config.php -mtime -90. Check access logs for beeteam368 requests with path traversal. Review database for unauthorized admin users.

Is deactivating the plugin sufficient?

Deactivating prevents new exploitation but does not remove the vulnerable files. You must delete the plugin entirely. Also audit for compromise — if already exploited, the attacker may have planted backdoors elsewhere.

Related PHP CVEs

CVE-2025-62521CVSS 10ChurchCRM is an open-source church management system. Prior to version 5.21.0, a pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard allows unauthenticated attackers to inject arbitrary PHP code during the initial installation process, leading to complete server compromise. The vulnerability exists in `setup/routes/setup.php` where user input from the setup form is directly concatenated into a PHP configuration template without any validation or sanitization. Any parameter in the setup form can be used to inject PHP code that gets written to `Include/Config.php`, which is then executed on every page load. This is more severe than typical authenticated RCE vulnerabilities because it requires no credentials and affects the installation process that administrators must complete. Version 5.21.0 patches the issue.
CVE-2025-46348CVSS 10YesWiki is a wiki system written in PHP. Prior to version 4.5.4, the request to commence a site backup can be performed and downloaded without authentication. The archives are created with a predictable filename, so a malicious user could create and download an archive without being authenticated. This could result in a malicious attacker making numerous requests to create archives and fill up the file system, or by downloading the archive which contains sensitive site information. This issue has been patched in version 4.5.4.
CVE-2026-39337CVSS 10ChurchCRM is an open-source church management system. Prior to 7.1.0, critical pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard allows unauthenticated attackers to inject arbitrary PHP code during the initial installation process, leading to complete server compromise. The "$dbPassword" variable is not sanitized. This vulnerability exists due to an incomplete fix for CVE-2025-62521. This vulnerability is fixed in 7.1.0.
CVE-2024-5932CVSS 10The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.14.1 via deserialization of untrusted input from the 'give_title' parameter. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to execute code remotely, and to delete arbitrary files.
CVE-2026-28289CVSS 10FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. A patch bypass vulnerability for CVE-2026-27636 in FreeScout 1.8.206 and earlier allows any authenticated user with file upload permissions to achieve Remote Code Execution (RCE) on the server by uploading a malicious .htaccess file using a zero-width space character prefix to bypass the security check. The vulnerability exists in the sanitizeUploadedFileName() function in app/Http/Helper.php. The function contains a Time-of-Check to Time-of-Use (TOCTOU) flaw where the dot-prefix check occurs before sanitization removes invisible characters. This vulnerability is fixed in 1.8.207.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2025-25174. Free for 1 server.

Get started free