Weakness (CWE)
CWE-98: PHP Remote File Inclusion"
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.
How to prevent it (8 mitigations)
-
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 example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.
This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.
Be careful to avoid CWE-243 and other weaknesses related to jails.
-
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 administrator, especially in day-to-day operations.
-
Implementation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
When validating filenames, use stringent lists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.
Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.
-
Architecture and Design, Operation
Store library, include, and utility files outside of the web document root, if possible. Otherwise, store them in a separate directory and use the web server's access control capabilities to prevent attackers from directly requesting them. One common practice is to define a fixed constant in each calling program, then check for the existence of the constant in the library/include file; if the constant does not exist, then the file was directly requested, and it can exit immediately.
This significantly reduces the chance of an attacker being able to bypass any protection mechanisms that are in the base program but not in the include files. It will also reduce the attack surface.
-
Architecture and Design, Implementation
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
Many file inclusion problems occur because the programmer assumed that certain inputs could not be modified, especially for cookies and URL components.
Source: MITRE CWE-98
1,217 results · Clear filters · Feed
-
High 8.8
WordPress WpTravelly plugin <= 2.3.8 - Local File Inclusion vulnerability
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Magepeople inc. WpTravelly tour-booking-manager allows PHP Local File Inclusion.This issue affects WpTravelly: from n/a through 2.3.8.
-
High 8.8
WordPress WpTravelly plugin <= 2.3.8 - Local File Inclusion vulnerability
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Magepeople inc. WpTravelly tour-booking-manager allows PHP Local File Inclusion.This issue affects WpTravelly: from n/a through 2.3.8.
-
High 8.8
Control Web Panel (CWP) < 1.16 Path Traversal via services/users/index.php
Control Web Panel (CWP) before webpanel_version 1.16 contains a path traversal vulnerability in services/users/index.php that allows attackers to include arbitrary local PHP files by supplying an unsanitized module name parameter concatenated directly into an…
-
High 7.5
DedeCMS < 5.7 File Inclusion via plus/carbuyaction.php
DedeCMS before 5.7 contains a file inclusion vulnerability in plus/carbuyaction.php that allows remote unauthenticated attackers to control the include path by manipulating the uninitialized code parameter passed to require_once. Attackers can supply path tra…
-
High 8.1
WordPress Your Dress theme <= 1.4.1 - Local File Inclusion vulnerability
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in AncoraThemes Your Dress your-dress allows PHP Local File Inclusion.This issue affects Your Dress: from n/a through 1.4.1.
-
High 7.5
Broadstreet Ad Widget WordPress Plugin < 2.12.0 Local File Inclusion via step parameter
Broadstreet Ad Widget plugin for WordPress 2.2.0 before 2.12.0 contains a local file inclusion vulnerability that allows authenticated users to execute attacker-chosen PHP files by passing unsanitized input to require in views/modal/index.php. Attackers can s…
-
High 8.1
WordPress Academist Core plugin <= 1.4.1 - Local File Inclusion vulnerability
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Elated-Themes Academist Core academist-core allows PHP Local File Inclusion.This issue affects Academist Core: from n/a through 1.4.1.
-
High 8.1
Issuu Panel WordPress Plugin < 1.6.6 File Inclusion via ajax-docs.php
Issuu Panel plugin for WordPress before 1.6.6 contains a PHP file inclusion vulnerability that allows unauthenticated attackers to include remote or local files through the 'abspath' parameter. Attackers can send GET requests to menu/documento/requests/ajax-d…
-
High 8.1
Mang Board <= 2.4.3 - Unauthenticated Local File Inclusion via '<mode>_type' Parameter
The Mang Board plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.4.3 via the '<mode>_type (e.g. foo_type)' parameter parameter. This makes it possible for unauthenticated attackers to include and execute arbitr…
-
High 7.5
LifterLMS <= 10.3.1 - Authenticated (Contributor+) Local File Inclusion via 'lifterlms_checkout' Shortcode Attributes
The LifterLMS – WP LMS for eLearning, Online Courses, & Quizzes plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 10.3.1 via attacker-controlled attributes of the [lifterlms_checkout] shortcode. This is due to the ll…
-
High 8.1
ShopMagic <= 4.9.0 - Unauthenticated Local File Inclusion via 'billing.first_name' Parameter
The ShopMagic – email automation for WordPress plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.9.0 via the 'billing_address.first_name' parameter parameter. This makes it possible for unauthenticated attacker…
-
High 8.1
BP Profile Search <= 5.9 - Unauthenticated Local File Inclusion to Remote Code Execution via 'bps_directory' Cookie 'ajax_template' Value
The BP Profile Search plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 5.9 via the 'ajax_template' value parsed from the client-controlled 'bps_directory' cookie during BuddyPress AJAX directory requests. The bps_di…
-
High 8.1
WordPress Ambient theme <= 1.7 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in Ambient <= 1.7 versions.
-
High 8.1
WordPress KuteShop theme <= 4.2.9 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in KuteShop <= 4.2.9 versions.
-
High 8.1
WordPress Boutique theme <= 2.3.3 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in Boutique <= 2.3.3 versions.
-
High 8.1
WordPress Biolife theme <= 3.2.3 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in Biolife <= 3.2.3 versions.
-
High 8.1
WordPress TechOne theme <= 3.0.3 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in TechOne <= 3.0.3 versions.
-
High 8.1
WordPress Armania theme <= 1.4.8 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in Armania <= 1.4.8 versions.
-
High 8.1
WordPress Backhoe theme <= 2.0 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in Backhoe <= 2.0 versions.
-
High 8.1
WordPress Ozeum theme <= 1.3.0 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in Ozeum <= 1.3.0 versions.
-
High 8.1
WordPress Flipmart theme <= 2.8 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in Flipmart <= 2.8 versions.
-
High 8.1
WordPress Teoro theme <= 1.1 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in Teoro <= 1.1 versions.
-
High 8.1
WordPress Fabius theme <= 1.0 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in Fabius <= 1.0 versions.
-
High 8.1
WordPress Kaven theme <= 1.2 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in Kaven <= 1.2 versions.
-
High 8.1
WordPress Volos theme <= 1.2 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in Volos <= 1.2 versions.
-
High 8.1
WordPress Cardea theme <= 2.3 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in Cardea <= 2.3 versions.
-
High 8.1
WordPress TouchUp theme < 1.4 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in TouchUp < 1.4 versions.
-
High 8.1
WordPress DukaMarket theme <= 1.3.0 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in DukaMarket <= 1.3.0 versions.
-
High 8.1
WordPress Uminex theme <= 1.0.9 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in Uminex <= 1.0.9 versions.
-
High 8.1
WordPress CleanSkin theme <= 1.5.0 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in CleanSkin <= 1.5.0 versions.
-
High 8.1
WordPress Aalto theme <= 1.8 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in Aalto <= 1.8 versions.
-
High 8.1
WordPress Kids Care theme <= 3.2.4 - Local File Inclusion vulnerability
Unauthenticated Local File Inclusion in Kids Care <= 3.2.4 versions.
-
High 8.1
GeoDirectory <= 2.8.187 - Unauthenticated Local File Inclusion via 'design_type' Parameter
The GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.8.187 via the 'design_type' parameter parameter. This makes it possible for un…
-
High 8.1
WordPress The Voux theme <= 6.9.5 - Local File Inclusion vulnerability
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Fuelthemes The Voux thevoux-wp allows PHP Local File Inclusion.This issue affects The Voux: from n/a through 6.9.5.
-
High 8.1
WordPress Werkstatt theme <= 4.8.3 - Local File Inclusion vulnerability
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Fuelthemes Werkstatt werkstatt allows PHP Local File Inclusion.This issue affects Werkstatt: from n/a through 4.8.3.
-
High 7.5
WPCafe <= 3.0.18 - Authenticated (Contributor+) Local File Inclusion via 'food_menu_style' Elementor Widget Setting
The WPCafe – Restaurant Menu, Online Food Ordering & Table Booking System plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.0.18 via the (template scope) function. This makes it possible for authenticated attac…
-
High 7.5
SiteOrigin Widgets Bundle <= 1.73.2 - Authenticated (Contributor+) Local File Inclusion via 'theme' Parameter
The SiteOrigin Widgets Bundle plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.73.2 via the 'theme' parameter parameter. This makes it possible for authenticated attackers, with contributor-level access and ab…
-
High 7.1
GetSimple CMS: Authenticated Stored Local File Inclusion (LFI) via page "template" field
GetSimple CMS is a content management system (CMS), and GetSimple CMS CE is the community edition of that CMS. In versions 3.3.22 and prior, an authenticated user with page-editing rights can store an arbitrary filesystem path in a page's template attribute. …
-
High 8.8
WordPress CartFlows plugin <= 3.2.0 - Remote Code Execution (RCE) vulnerability
Contributor Remote Code Execution (RCE) in CartFlows <= 3.2.0 versions.
-
High 7.5
Simply Schedule Appointments <= 1.6.12.27 - Authenticated (Subscriber+) Local File Inclusion via 'ssa_locale' Parameter
The Simply Schedule Appointments plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.6.12.27 via the 'ssa_locale' parameter parameter. This makes it possible for authenticated attackers, with subscriber-level acc…