high CVSS 7.5 EPSS 0.42%

CVE-2025-30871·PHP vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in WP Travel Engine WP Travel Engine wp-travel-engine allows PHP Local File Inclusion.This issue affects WP Travel Engine: from n/a through <= 6.3.5.

Severity
high
Software
PHP
Fixed in
6.3.6
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.42% — higher than 62% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Read the two together. CVE-2025-30871 scores 7.5 on CVSS, so a successful attack would be serious — but at 0.42%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.

Affected versions

Until: 6.3.6

Fixed in: 6.3.6

How to fix this CVE

Update the WP Travel Engine plugin to version 6.3.6 or later to patch the local file inclusion vulnerability. This vulnerability allows authenticated attackers to read arbitrary files from the server filesystem through improper input handling in file inclusion statements. Immediately apply the update and verify the plugin version matches or exceeds 6.3.6 in your WordPress dashboard.

sudo dnf update php

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST|GET /wp-content/plugins/wp-travel-engine/.*(include|require|file|path).*=.*(\.\.[\/\\]|%2e%2e%2f|\.\.%5c|etc%2fpasswd)

WAF mitigation (if patching is not yet possible)

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

Implement input validation rules to block requests containing path traversal patterns (../, ..\, %2e%2e%2f) in parameters passed to the wp-travel-engine plugin endpoints. Rate-limit POST requests to plugin file handlers and require authentication validation before processing file inclusion requests.

How to check if you are affected

  1. Step 1: Check PHP version with `php -v` and verify WP Travel Engine plugin version by running `wp plugin list --format=table | grep wp-travel-engine` (requires WP-CLI) or manually inspect the wp-content/plugins/wp-travel-engine/wp-travel-engine.php file for the Version header
  2. Step 2: Query the WordPress options table to confirm the plugin is active: `wp option get active_plugins | grep wp-travel-engine`
  3. Step 3: Search web server logs (Apache: /var/log/apache2/access.log, Nginx: /var/log/nginx/access.log) for suspicious file inclusion patterns such as path traversal sequences (../, ..\ or encoded variants %2e%2e%2f) targeting plugin URLs like /wp-content/plugins/wp-travel-engine/
  4. Step 4: After updating, verify the patch with `wp plugin list --format=table | grep wp-travel-engine` to confirm version is 6.3.6 or higher

FAQ

What is CVE-2025-30871?

CVE-2025-30871 is a local file inclusion (LFI) vulnerability in WP Travel Engine plugin versions up to 6.3.5 that allows authenticated users to read sensitive files from the server by manipulating file path parameters in include/require statements. This could expose database credentials, configuration files, or other sensitive data.

Is CVE-2025-30871 being actively exploited?

No, CVE-2025-30871 is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. However, the vulnerability requires authentication and presents a real risk if left unpatched.

What versions of PHP are affected by CVE-2025-30871?

The vulnerability affects WP Travel Engine plugin versions from initial release through 6.3.5. The fixed version is 6.3.6 and later. This is a plugin vulnerability, not a PHP core issue, but it impacts WordPress installations using this plugin.

How do I check if my server is vulnerable to CVE-2025-30871?

Log into your WordPress admin dashboard, navigate to Plugins, and check the WP Travel Engine version. If it shows 6.3.5 or earlier, your installation is vulnerable. Alternatively, run `wp plugin list` via WP-CLI and verify the version number.

Does Defensia detect CVE-2025-30871?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If PHP and the WP Travel Engine plugin are installed on a monitored server, CVE-2025-30871 will appear in your dashboard with remediation steps.

Related PHP CVEs

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-2025-47916CVSS 10Invision Community 5.0.0 before 5.0.7 allows remote code execution via crafted template strings to themeeditor.php. The issue lies within the themeeditor controller (file: /applications/core/modules/front/system/themeeditor.php), where a protected method named customCss can be invoked by unauthenticated users. This method passes the value of the content parameter to the Theme::makeProcessFunction() method; hence it is evaluated by the template engine. Accordingly, this can be exploited by unauthenticated attackers to inject and execute arbitrary PHP code by providing crafted template strings.
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-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-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-30871. Free for 1 server.

Get started free