View GitHub Repository humhub-themes-flathub

Schedule Inspection
Subscribe

Issues (8)

Security Analysis    no request data  

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

  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.
  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.
  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.
  Code Injection
Code Injection enables an attacker to execute arbitrary code on the server.
  Response Splitting
Response Splitting can be used to send arbitrary responses.
  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.
  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.
  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.
  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.
  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.
  Header Injection
  Other Vulnerability
This category comprises other attack vectors such as manipulating the PHP runtime, loading custom extensions, freezing the runtime, or similar.
  Regex Injection
Regex Injection enables an attacker to execute arbitrary code in your PHP process.
  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.
  Variable Injection
Variable Injection enables an attacker to overwrite program variables with custom data, and can lead to further vulnerabilities.
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.

views/user/widgets/AccountMenu.php (1 issue)

← previous file next file →

Upgrade to new PHP Analysis Engine

These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more

Code
1 
<?php
2 
/**
3 
 * @link https://www.humhub.org/
4 
 * @copyright Copyright (c) 2015 HumHub GmbH & Co. KG
5 
 * @license https://www.humhub.com/licences
6 
 */
7 
namespace humhub\modules\user\widgets;
8 
use Yii;
9 
use \humhub\widgets\BaseMenu;
10 
use \yii\helpers\Url;
11 
/**
12 
 * AccountMenuWidget as (usally left) navigation on users account options.
13 
 *
14 
 * @package humhub.modules_core.user.widgets
15 
 * @since 0.5
16 
 * @author Luke
17 
 */
18 
class AccountMenu extends BaseMenu
19 
{
20 
    public $template = "@humhub/widgets/views/leftNavigation";
21 
    public $type = "accountNavigation";
22 
    public function init()
23 
    {
24 
        $controllerAction = Yii::$app->controller->action->id;
25 
        $this->addItemGroup(array(
26 
            'id' => 'account',
27 
            'label' => Yii::t('UserModule.widgets_AccountMenuWidget', '<strong>Account</strong> settings'),
28 
            'sortOrder' => 100,
29 
        ));
30 
        $this->addItem(array(
31 
            'label' => Yii::t('UserModule.widgets_AccountMenuWidget', 'Profile'),
32 
            'icon' => '<i class="fa fa-user"></i>',
33 
            'group' => 'account',
34 
            'url' => Url::toRoute('/user/account/edit'),
35 
            'sortOrder' => 100,
36 
            'isActive' => ($controllerAction == "edit" || $controllerAction == "change-email" || $controllerAction == "change-password" || $controllerAction == "delete"),
37 
        ));
38 
        $this->addItem(array(
39 
            'label' => Yii::t('UserModule.account', 'E-Mail Summaries'),
40 
            'icon' => '<i class="fa fa-envelope"></i>',
41 
            'group' => 'account',
42 
            'url' => Url::toRoute('/activity/user'),
43 
            'sortOrder' => 105,
44 
            'isActive' => (Yii::$app->controller->module->id == 'activity'),
45 
        ));
46
47 
        $this->addItem(array(
48 
            'label' => Yii::t('UserModule.account', 'Notifications'),
49 
            'icon' => '<i class="fa fa-bell"></i>',
50 
            'group' => 'account',
51 
            'url' => Url::toRoute('/notification/user'),
52 
            'sortOrder' => 106,
53 
            'isActive' => (Yii::$app->controller->module->id == 'notification'),
54 
        ));
55 
        $this->addItem(array(
56 
            'label' => Yii::t('UserModule.widgets_AccountMenuWidget', 'Settings'),
57 
            'icon' => '<i class="fa fa-wrench"></i>',
58 
            'group' => 'account',
59 
            'url' => Url::toRoute('/user/account/edit-settings'),
60 
            'sortOrder' => 110,
61 
            'isActive' => ($controllerAction == "edit-settings"),
62 
        ));
63 
        $this->addItem(array(
64 
            'label' => Yii::t('UserModule.widgets_AccountMenuWidget', 'Security'),
65 
            'icon' => '<i class="fa fa-lock"></i>',
66 
            'group' => 'account',
67 
            'url' => Url::toRoute('/user/account/security'),
68 
            'sortOrder' => 115,
69 
            'isActive' => (Yii::$app->controller->action->id == "security"),
70 
        ));
71 
        // Only show this page when really user specific modules available
72 
        if (count(Yii::$app->user->getIdentity()->getAvailableModules()) != 0) {
73 
            $this->addItem(array(
74 
                'label' => Yii::t('UserModule.widgets_AccountMenuWidget', 'Modules'),
75 
                'icon' => '<i class="fa fa-rocket"></i>',
76 
                'group' => 'account',
77 
                'url' => Url::toRoute('//user/account/edit-modules'),
78 
                'sortOrder' => 120,
79 
                'isActive' => (Yii::$app->controller->action->id == "edit-modules"),
80 
            ));
81 
        }
82 
        parent::init();
83 
    }
84 
}
85 
?>
0 ignored issues
– show
Best Practice introduced by
It is not recommended to use PHP's closing tag ?> in files other than templates.

Using a closing tag in PHP files that only contain PHP code is not recommended as you might accidentally add whitespace after the closing tag which would then be output by PHP. This can cause severe problems, for example headers cannot be sent anymore.

A simple precaution is to leave off the closing tag as it is not required, and it also has no negative effects whatsoever.

Loading history...
86