Issues (807)

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.

class/Registry.php (3 issues)

1
<?php
2
3
namespace XoopsModules\Pedigree;
4
5
/*
6
 You may not change or alter any portion of this comment or credits
7
 of supporting developers from this source code or any supporting source code
8
 which is considered copyrighted (c) material of the original comment or credit authors.
9
10
 This program is distributed in the hope that it will be useful,
11
 but WITHOUT ANY WARRANTY; without even the implied warranty of
12
 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
13
*/
14
15
/**
16
 * Module: Pedigree
17
 *
18
 * @category        Module
19
 * @package         pedigree
20
 * @author          XOOPS Development Team <https://xoops.org>
21
 * @copyright       {@link https://xoops.org/ XOOPS Project}
22
 * @license         GPL 2.0 or later
23
 * @link            https://xoops.org/
24
 * @since           1.0.0
25
 */
26
27
use Xmf\Module\Helper\Permission;
28
use XoopsModules\Pedigree\{
29
    Helper
0 ignored issues
show
This use statement conflicts with another class in this namespace, XoopsModules\Pedigree\Helper. 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...
30
};
31
32
33
//$permHelper = new \Xmf\Module\Helper\Permission();
34
35
/**
36
 * Class Registry
37
 */
38
class Registry extends \XoopsObject
39
{
40
    public $helper;
41
    public $permHelper;
42
43
    /**
44
     * Constructor
45
     *
46
     * @param null
47
     */
48
    public function __construct()
49
    {
50
        parent::__construct();
51
        /** @var Pedigree\Helper $helper */
52
        $this->helper     = Helper::getInstance();
53
        $this->permHelper = new Permission();
54
55
        $this->initVar('id', \XOBJ_DTYPE_INT);
56
        $this->initVar('pname', \XOBJ_DTYPE_OTHER);
57
        $this->initVar('id_owner', \XOBJ_DTYPE_INT);
58
        $this->initVar('id_breeder', \XOBJ_DTYPE_INT);
59
        $this->initVar('user', \XOBJ_DTYPE_TXTBOX);
60
        $this->initVar('roft', \XOBJ_DTYPE_ENUM);
61
        $this->initVar('mother', \XOBJ_DTYPE_INT);
62
        $this->initVar('father', \XOBJ_DTYPE_INT);
63
        $this->initVar('foto', \XOBJ_DTYPE_TXTBOX);
64
        $this->initVar('coi', \XOBJ_DTYPE_TXTBOX);
65
    }
66
67
    /**
68
     * Get form
69
     *
70
     * @param null
71
     * @return Pedigree\Form\RegistryForm
0 ignored issues
show
The type XoopsModules\Pedigree\Pedigree\Form\RegistryForm was not found. Maybe you did not declare it correctly or list all dependencies?

The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g. excluded_paths: ["lib/*"], you can move it to the dependency path list as follows:

filter:
    dependency_paths: ["lib/*"]

For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths

Loading history...
72
     */
73
    public function getForm()
74
    {
75
        $form = new Form\RegistryForm($this);
76
77
        return $form;
0 ignored issues
show
Bug Best Practice introduced by
The expression return $form returns the type XoopsModules\Pedigree\Form\RegistryForm which is incompatible with the documented return type XoopsModules\Pedigree\Pedigree\Form\RegistryForm.
Loading history...
78
    }
79
80
    /**
81
     * @return array|null
82
     */
83
    public function getGroupsRead()
84
    {
85
        //$permHelper = new \Xmf\Module\Helper\Permission();
86
        return $this->permHelper->getGroupsForItem('sbcolumns_read', $this->getVar('id'));
87
    }
88
89
    /**
90
     * @return array|null
91
     */
92
    public function getGroupsSubmit()
93
    {
94
        //$permHelper = new \Xmf\Module\Helper\Permission();
95
        return $this->permHelper->getGroupsForItem('sbcolumns_submit', $this->getVar('id'));
96
    }
97
98
    /**
99
     * @return array|null
100
     */
101
    public function getGroupsModeration()
102
    {
103
        //$permHelper = new \Xmf\Module\Helper\Permission();
104
        return $this->permHelper->getGroupsForItem('sbcolumns_moderation', $this->getVar('id'));
105
    }
106
}
107