Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-pagenavi domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/u918112125/domains/exploit.company/public_html/wp-includes/functions.php on line 6114
Multiple Remote File-Include Vulnerabilities in DataLife Engine - exploit.company
header-logo
Suggest Exploit
vendor:
DataLife Engine
by:
Unknown
7.5
CVSS
HIGH
Remote File Inclusion
CWE
Product Name: DataLife Engine
Affected Version From: Unknown
Affected Version To: Unknown
Patch Exists: NO
Related CWE:
CPE:
Metasploit:
Other Scripts:
Platforms Tested:
Unknown

Multiple Remote File-Include Vulnerabilities in DataLife Engine

An attacker can exploit these issues to include an arbitrary remote file containing malicious PHP code and execute it in the context of the webserver process. This may allow the attacker to compromise the application and the underlying system; other attacks are also possible.

Mitigation:

This vulnerability has been retired as the reported vulnerable parameter is actually a constant, not a variable, so it cannot be controlled by an attacker. No action is required.
Source

Exploit-DB raw data:

source: https://www.securityfocus.com/bid/22913/info

DataLife Engine is prone to multiple remote file-include vulnerabilities.

An attacker can exploit these issues to include an arbitrary remote file containing malicious PHP code and execute it in the context of the webserver process. This may allow the attacker to compromise the application and the underlying system; other attacks are also possible.

NOTE: Further information reveals that the reported vulnerable parameter is actually a constant, not a variable, so it cannot be controlled by an attacker. Since the application is not vulnerable, this BID is being retired.

http://www.example.com/engine/init.php?root_dir=[Shell-Attack]