Issues (55)

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.

classes/Driver.php (3 issues)

Severity

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

1
<?php namespace Bedard\Shop\Classes;
2
3
use Bedard\Shop\Models\DriverConfig;
4
use Exception;
5
use October\Rain\Exception\ValidationException;
6
use October\Rain\Parse\Yaml;
7
use ReflectionClass;
8
use Validator;
9
10
abstract class Driver
11
{
12
    /**
13
     * @var array Custom validation messages.
14
     */
15
    public $customMessages = [];
16
17
    /**
18
     * @return string Form fields.
19
     */
20
    public $formFields;
21
22
    /**
23
     * @var array Validation rules.
24
     */
25
    public $rules = [];
26
27
    /**
28
     * After validate.
29
     *
30
     * @param  array    $data
31
     * @return void
32
     */
33
    public function afterValidate(array $data)
0 ignored issues
show
The parameter $data is not used and could be removed.

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

Loading history...
34
    {
35
    }
36
37
    /**
38
     * Before validate.
39
     *
40
     * @param  array    $data
41
     * @return void
42
     */
43
    public function beforeValidate(array $data)
0 ignored issues
show
The parameter $data is not used and could be removed.

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

Loading history...
44
    {
45
    }
46
47
    /**
48
     * Get the configuration model.
49
     *
50
     * @return Bedard\Shop\Models\DriverConfig
51
     */
52
    public function getConfigModel()
53
    {
54
        return DriverConfig::firstOrNew([
55
            'class' => get_class($this),
56
        ]);
57
    }
58
59
    /**
60
     * Get the configuration array.
61
     *
62
     * @return array
63
     */
64
    public function getConfig()
65
    {
66
        $model = $this->getConfigModel();
67
68
        return $model->getConfig();
69
    }
70
71
    /**
72
     * Get form fields.
73
     *
74
     * @return array
75
     */
76
    public function getFormFields()
77
    {
78
        if (! $this->formFields) {
79
            throw new Exception('Drivers must define a $formFields property, or overwrite the getFormFields() method.');
80
        }
81
82
        if (! is_string($this->formFields)) {
83
            throw new Exception('Driver $formFields property must be a string.');
84
        }
85
86
        $yaml = new Yaml;
87
88
        $reflector = new ReflectionClass(get_class($this));
89
90
        return $yaml->parseFile(dirname($reflector->getFileName()).'/'.$this->formFields);
91
    }
92
93
    /**
94
     * Save driver configuration.
95
     *
96
     * @param  array    $config
97
     * @return void
98
     */
99
    public function saveConfig(array $config)
100
    {
101
        $this->validate($config);
102
103
        $model = $this->getConfigModel(false);
0 ignored issues
show
The call to Driver::getConfigModel() has too many arguments starting with false.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
104
105
        $model->config = json_encode($config);
106
107
        return $model->save();
108
    }
109
110
    /**
111
     * Validate form data.
112
     *
113
     * @param  array $formData
114
     * @return void
115
     * @throws \October\Rain\Exception\ValidationException
116
     */
117
    public function validate(array $formData)
118
    {
119
        $this->beforeValidate($formData);
120
121
        $validator = Validator::make($formData, $this->rules, $this->customMessages);
122
123
        if ($validator->fails()) {
124
            throw new ValidationException($validator);
125
        }
126
127
        $this->afterValidate($formData);
128
    }
129
}
130