Issues in permissions.php (master) - Issues in master - XoopsModules25x/xwhoops25 - Measure and Improve Code Quality continuously with Scrutinizer

Issues (9)

Security Analysis no request data

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.

admin/permissions.php (1 issue)

Labels

Bug 1

Severity

<?php declare(strict_types=1);
/*
 You may not change or alter any portion of this comment or credits
 of supporting developers from this source code or any supporting source code
 which is considered copyrighted (c) material of the original comment or credit authors.

 This program is distributed in the hope that it will be useful,
 but WITHOUT ANY WARRANTY; without even the implied warranty of
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
 */

/**
 * @copyright 2019-2021 XOOPS Project (https://xoops.org)
 * @license   GNU GPL 2.0 or later (https://www.gnu.org/licenses/gpl-2.0.html)
 * @author    Richard Griffith <[email protected]>
 */

use Xmf\Module\Admin;
use Xmf\Module\Helper;
use Xmf\Module\Helper\Permission;
use Xmf\Request;
.
|-- OtherDir
|   |-- Bar.php
|   `-- Foo.php
`-- SomeDir
    `-- Foo.php

require_once __DIR__ . '/admin_header.php';

require_once XOOPS_ROOT_PATH . '/class/xoopsformloader.php';

$moduleAdmin = Admin::getInstance();
$moduleAdmin->displayNavigation('permissions.php');

$helper     = Helper::getHelper('xwhoops');
$permHelper = new Permission();
if ($permHelper) {
    // this is the name and item we are going to work with
    $permissionName   = 'use_xwhoops';
    $permissionItemId = 0;

    // if this is a post operation get our variables
    if ('POST' === Request::getMethod()) {
        if (!$GLOBALS['xoopsSecurity']->check()) {
            redirect_header(XOOPS_URL . '/', 3, $GLOBALS['xoopsSecurity']->getErrors());
        }
        $name   = $permHelper->defaultFieldName($permissionName, $permissionItemId);
        $groups = Request::getVar($name, [], 'POST');
        $permHelper->savePermissionForItem($permissionName, $permissionItemId, $groups);
        xoops_result(_MA_XWHOOPS_FORM_PROCESSED, _MA_XWHOOPS_PERMISSION_FORM);
    }
    $form        = new XoopsThemeForm(_MA_XWHOOPS_PERMISSION_FORM, 'form', '', 'POST', true);
    $permElement = $permHelper->getGroupSelectFormForItem(
        $permissionName,
        $permissionItemId,
        _MA_XWHOOPS_PERMISSION_GROUPS,
        null,
        true
    );

    $form->addElement($permElement);
    $form->addElement(new XoopsFormButton('', 'submit', _MA_XWHOOPS_FORM_SUBMIT, 'submit'));

    echo $form->render();
}

require_once __DIR__ . '/admin_footer.php';


1			<?php declare(strict_types=1);
2			/*
3			You may not change or alter any portion of this comment or credits
4			of supporting developers from this source code or any supporting source code
5			which is considered copyrighted (c) material of the original comment or credit authors.
6
7			This program is distributed in the hope that it will be useful,
8			but WITHOUT ANY WARRANTY; without even the implied warranty of
9			MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
10			*/
11
12			/**
13			* @copyright 2019-2021 XOOPS Project (https://xoops.org)
14			* @license GNU GPL 2.0 or later (https://www.gnu.org/licenses/gpl-2.0.html)
15			* @author Richard Griffith <[email protected]>
16			*/
17
18			use Xmf\Module\Admin;
19			use Xmf\Module\Helper;
20			use Xmf\Module\Helper\Permission;
21			use Xmf\Request;
			0 ignored issues – show Bug introduced 2025-06-08 04:31 UTC by Report Bug Copy Issue Report Show Similar Issues like this This use statement conflicts with another class in this namespace, `Request`. Consider defining an alias. Let?s assume that you have a directory layout like this: . \|-- OtherDir \| \|-- Bar.php \| `-- Foo.php `-- SomeDir `-- Foo.php and let?s assume the following content of `Bar.php`: // Bar.php namespace OtherDir; use SomeDir\Foo; // This now conflicts the class OtherDir\Foo If both files `OtherDir/Foo.php` and `SomeDir/Foo.php` are loaded in the same runtime, you will see a PHP error such as the following: PHP Fatal error: Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.php However, as `OtherDir/Foo.php` does not necessarily have to be loaded and the error is only triggered if it is loaded before `OtherDir/Bar.php`, this problem might go unnoticed for a while. In order to prevent this error from surfacing, you must import the namespace with a different alias: // Bar.php namespace OtherDir; use SomeDir\Foo as SomeDirFoo; // There is no conflict anymore. Loading history...
22
23			require_once __DIR__ . '/admin_header.php';
24
25			require_once XOOPS_ROOT_PATH . '/class/xoopsformloader.php';
26
27			$moduleAdmin = Admin::getInstance();
28			$moduleAdmin->displayNavigation('permissions.php');
29
30			$helper = Helper::getHelper('xwhoops');
31			$permHelper = new Permission();
32			if ($permHelper) {
33			// this is the name and item we are going to work with
34			$permissionName = 'use_xwhoops';
35			$permissionItemId = 0;
36
37			// if this is a post operation get our variables
38			if ('POST' === Request::getMethod()) {
39			if (!$GLOBALS['xoopsSecurity']->check()) {
40			redirect_header(XOOPS_URL . '/', 3, $GLOBALS['xoopsSecurity']->getErrors());
41			}
42			$name = $permHelper->defaultFieldName($permissionName, $permissionItemId);
43			$groups = Request::getVar($name, [], 'POST');
44			$permHelper->savePermissionForItem($permissionName, $permissionItemId, $groups);
45			xoops_result(_MA_XWHOOPS_FORM_PROCESSED, _MA_XWHOOPS_PERMISSION_FORM);
46			}
47			$form = new XoopsThemeForm(_MA_XWHOOPS_PERMISSION_FORM, 'form', '', 'POST', true);
48			$permElement = $permHelper->getGroupSelectFormForItem(
49			$permissionName,
50			$permissionItemId,
51			_MA_XWHOOPS_PERMISSION_GROUPS,
52			null,
53			true
54			);
55
56			$form->addElement($permElement);
57			$form->addElement(new XoopsFormButton('', 'submit', _MA_XWHOOPS_FORM_SUBMIT, 'submit'));
58
59			echo $form->render();
60			}
61
62			require_once __DIR__ . '/admin_footer.php';
63

XoopsModules25x / xwhoops25

Issues (9)

Security Analysis no request data

admin/permissions.php (1 issue)

Labels

Severity

Introduced By

Duplication Side-by-Side

Filter issues like