7 matches found
CVE-2022-4063
The InPost Gallery WordPress plugin before 2.1.4.1 insecurely uses PHP's extract function when rendering HTML views, allowing attackers to force the inclusion of malicious files & URLs, which may enable them to run code on servers...
CVE-2022-4063
The InPost Gallery WordPress plugin before 2.1.4.1 insecurely uses PHP's extract function when rendering HTML views, allowing attackers to force the inclusion of malicious files & URLs, which may enable them to run code on servers...
Abtp Portal Project 0.1.0 - Local File Inclusion
!/usr/bin/perl =about ---------------------------------------------------------------------------------------------------- Name : Abtp Portal Project The variable $ ABTPVBLOQUECENTRAL was not correctly stated thus enabling the attack include malicious files or read files from the system. If...
Golabi CMS 1.0.1 Session Poisoning
-------------------------------------------------------------------------------- \ \ / \ | | / \ /\ \ \ \ /| | \ /|| / / | /| /\ / \ / / / // / /// / -------------------------------------------------------------------------------- wWw.CrazyAngel.iR - info-AT-CrazyAngel.iR...
mboard-rfi.txt
mboard remote file include By: e.wiZz! Site: madspot.org In the wild... Script site: http://www.phpjunkyard.com/php-message-board.php Download: http://www.phpjunkyard.com/download.php?script=mboard Vulnerable file: mboard.php Vulnerable code: if fileexists$file includeonce$file; else Exploit:...
RE: [NOBYTES.COM: #6] CubeCart 2.0.6 - Information Disclosure
Hello, http://www.victimsite.com/index.php?&language=f00bar.php Warning: Failed opening '/var/www/html/admin/lang/f00bar.php' for inclusion includepath='.:/usr/share/pear' in /var/www/html/admin/settings.inc.php on line 147 This is path disclosure but it can also be used for malicious file includ...
SPChat 0.8 Module - Remote File Inclusion
SPChat 0.8 Module - Remote File Inclusion source: https://www.securityfocus.com/bid/7780/info SPChat has been reported prone to a remote file include vulnerability. The issue presents itself due to insufficient sanitization performed on the user-supplied URI variable 'statussess' by the SPChat...