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
Campsite Multiple Remote File-Include Vulnerabilities - exploit.company
header-logo
Suggest Exploit
vendor:
Campsite CMS
by:
7.5
CVSS
HIGH
Remote File Inclusion
CWE
Product Name: Campsite CMS
Affected Version From: Campsite 2.6.1
Affected Version To: Campsite 2.6.1
Patch Exists: NO
Related CWE:
CPE:
Metasploit:
Other Scripts:
Platforms Tested:

Campsite Multiple Remote File-Include Vulnerabilities

The Campsite CMS is prone to multiple remote file-include vulnerabilities. Exploiting this issue allows remote attackers to execute arbitrary code in the context of the web server. The vulnerability is due to insufficient input validation in the 'ArticleAttachment.php' script. A remote attacker can exploit this issue by sending a specially crafted HTTP request containing a malicious file path to the vulnerable script. Successful exploitation will result in the inclusion of the attacker's file, which will be executed in the context of the web server.

Mitigation:

To mitigate these vulnerabilities, it is recommended to apply the latest patches and updates provided by the vendor. Additionally, it is good security practice to restrict access to the vulnerable script and to implement proper input validation to prevent file inclusion attacks.
Source

Exploit-DB raw data:

source: https://www.securityfocus.com/bid/23874/info
  
Campsite is prone to multiple remote file-include vulnerabilities.
  
Exploiting this issue allows remote attackers to execute code in the context of the webserver.
  
This issue affects Campsite 2.6.1. Earlier versions may also be affected.

http://www.example.com/classes/ArticleAttachment.php?g_DocumentRoot=shell.txt?