Issues (76)

Security Analysis    not enabled

This project does not seem to handle request data directly as such no vulnerable execution paths were found.

  File Inclusion
File Inclusion enables an attacker to inject custom files into PHP's file loading mechanism, either explicitly passed to include, or for example via PHP's auto-loading mechanism.
  Regex Injection
Regex Injection enables an attacker to execute arbitrary code in your PHP process.
  SQL Injection
SQL Injection enables an attacker to execute arbitrary SQL code on your database server gaining access to user data, or manipulating user data.
  Response Splitting
Response Splitting can be used to send arbitrary responses.
  File Manipulation
File Manipulation enables an attacker to write custom data to files. This potentially leads to injection of arbitrary code on the server.
  Object Injection
Object Injection enables an attacker to inject an object into PHP code, and can lead to arbitrary code execution, file exposure, or file manipulation attacks.
  File Exposure
File Exposure allows an attacker to gain access to local files that he should not be able to access. These files can for example include database credentials, or other configuration files.
  XML Injection
XML Injection enables an attacker to read files on your local filesystem including configuration files, or can be abused to freeze your web-server process.
  Code Injection
Code Injection enables an attacker to execute arbitrary code on the server.
  Variable Injection
Variable Injection enables an attacker to overwrite program variables with custom data, and can lead to further vulnerabilities.
  XPath Injection
XPath Injection enables an attacker to modify the parts of XML document that are read. If that XML document is for example used for authentication, this can lead to further vulnerabilities similar to SQL Injection.
  Other Vulnerability
This category comprises other attack vectors such as manipulating the PHP runtime, loading custom extensions, freezing the runtime, or similar.
  Command Injection
Command Injection enables an attacker to inject a shell command that is execute with the privileges of the web-server. This can be used to expose sensitive data, or gain access of your server.
  LDAP Injection
LDAP Injection enables an attacker to inject LDAP statements potentially granting permission to run unauthorized queries, or modify content inside the LDAP tree.
  Cross-Site Scripting
Cross-Site Scripting enables an attacker to inject code into the response of a web-request that is viewed by other users. It can for example be used to bypass access controls, or even to take over other users' accounts.
  Header Injection
Unfortunately, the security analysis is currently not available for your project. If you are a non-commercial open-source project, please contact support to gain access.

include/oninstall.php (1 issue)

Severity
1
<?php declare(strict_types=1);
2
/*
3
 You may not change or alter any portion of this comment or credits of
4
 supporting developers from this source code or any supporting source code
5
 which is considered copyrighted (c) material of the original comment or credit
6
 authors.
7
8
 This program is distributed in the hope that it will be useful, but
9
 WITHOUT ANY WARRANTY; without even the implied warranty of
10
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
11
 */
12
13
/**
14
 * XoopsFaq installation scripts
15
 *
16
 * @author    Taiwen Jiang <[email protected]>
17
 * @author    ZySpec <[email protected]>
18
 * @copyright https://xoops.org 2001-2017 XOOPS Project
19
 * @license   https://www.gnu.org/licenses/gpl-2.0.html GNU Public License
20
 * @link      https://xoops.org XOOPS
21
 * @since     1.25
22
 */
23
24
use XoopsModules\Xoopsfaq\{
25
    Helper,
26
    Utility
27
};
28
29
/**
30
 * @internal {Make sure you PROTECT THIS FILE}
31
 */
32
if ((!defined('XOOPS_ROOT_PATH'))
33
    || !($GLOBALS['xoopsUser'] instanceof \XoopsUser)
34
    || !($GLOBALS['xoopsUser']->isAdmin())) {
35
    exit('Restricted access' . PHP_EOL);
36
}
37
38
/**
39
 * Prepares system prior to attempting to install module
40
 *
41
 *
42
 * @return bool true if ready to install, false if not
43
 */
44
function xoops_module_pre_install_xoopsfaq(XoopsModule $module)
45
{
46
    /** @var Utility $utilsClass */
47
    $xoopsSuccess = Utility::checkVerXoops($module);
48
    $phpSuccess   = Utility::checkVerPhp($module);
49
50
    return $xoopsSuccess && $phpSuccess;
51
}
52
53
/**
54
 * Performs tasks required during installation of the module
55
 *
56
 * @param XoopsModule $module
57
 *
58
 * @return bool true if installation successful, false if not
59
 */
60
function xoops_module_install_xoopsfaq(\XoopsModule $module)
0 ignored issues
show
The parameter $module is not used and could be removed. ( Ignorable by Annotation )

If this is a false-positive, you can also ignore this issue in your code via the ignore-unused  annotation

60
function xoops_module_install_xoopsfaq(/** @scrutinizer ignore-unused */ \XoopsModule $module)

This check looks for parameters that have been defined for a function or method, but which are not used in the method body.

Loading history...
61
{
62
    return true;
63
}
64