Issues (649)

Security Analysis    not enabled

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.

inc/functions.php (5 issues)

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
2
/**
3
 * Webino (http://webino.sk/)
4
 *
5
 * Useful development functions.
6
 *
7
 * @link        https://github.com/webino/WebinoDevLib/ for the canonical source repository
8
 * @copyright   Copyright (c) 2015-2017 Webino, s.r.o. (http://webino.sk/)
9
 * @license     BSD-3-Clause
10
 */
11
12
use Tracy\Debugger;
13
14
/**
15
 * Alias for var_dump()
16
 *
17
 * @param mixed $subject
18
 */
19
function d($subject) {
20
    var_dump($subject);
0 ignored issues
show
Security Debugging Code introduced by
var_dump($subject); looks like debug code. Are you sure you do not want to remove it? This might expose sensitive data.
Loading history...
21
}
22
23
/**
24
 * Diyng var_dump()
25
 *
26
 * @param mixed $subject
27
 */
28
function dd($subject) {
29
    var_dump($subject);
0 ignored issues
show
Security Debugging Code introduced by
var_dump($subject); looks like debug code. Are you sure you do not want to remove it? This might expose sensitive data.
Loading history...
30
    exit;
0 ignored issues
show
Coding Style Compatibility introduced by
The function dd() contains an exit expression.

An exit expression should only be used in rare cases. For example, if you write a short command line script.

In most cases however, using an exit expression makes the code untestable and often causes incompatibilities with other libraries. Thus, unless you are absolutely sure it is required here, we recommend to refactor your code to avoid its usage.

Loading history...
31
}
32
33
/**
34
 * Alias for print_r() scream
35
 *
36
 * @param mixed $subject
37
 */
38
function p($subject) {
39
    if (class_exists(Debugger::class)) {
40
        Debugger::dump($subject);
41
        return;
42
    }
43
    print_r($subject);
44
}
45
46
/**
47
 * Dying print_r() scream
48
 *
49
 * @param mixed $subject
50
 */
51
function pd($subject) {
52
    if (class_exists(Debugger::class)) {
53
        Debugger::dump($subject);
54
        exit;
0 ignored issues
show
Coding Style Compatibility introduced by
The function pd() contains an exit expression.

An exit expression should only be used in rare cases. For example, if you write a short command line script.

In most cases however, using an exit expression makes the code untestable and often causes incompatibilities with other libraries. Thus, unless you are absolutely sure it is required here, we recommend to refactor your code to avoid its usage.

Loading history...
55
    }
56
    print_r($subject);
57
    exit;
0 ignored issues
show
Coding Style Compatibility introduced by
The function pd() contains an exit expression.

An exit expression should only be used in rare cases. For example, if you write a short command line script.

In most cases however, using an exit expression makes the code untestable and often causes incompatibilities with other libraries. Thus, unless you are absolutely sure it is required here, we recommend to refactor your code to avoid its usage.

Loading history...
58
}
59
60
/**
61
 * Alias for print_r() return
62
 *
63
 * @param mixed $subject
64
 * @return string
65
 */
66
function pr($subject) {
67
    if (class_exists(Debugger::class)) {
68
        return Debugger::dump($subject, true);
69
    }
70
    return print_r($subject, true);
71
}
72
73
/**
74
 * Debugger bar dump
75
 *
76
 * @param mixed $subject
77
 */
78
function bd($subject) {
79
    if (class_exists(Debugger::class)) {
80
        Debugger::barDump($subject);
81
    }
82
}
83
84
/**
85
 * Web debugger break point
86
 *
87
 * Sometimes is useful by throwing an exception to check a backtrace.
88
 *
89
 * @link https://github.com/webino/WebinoDebugLib Web debugger
90
 * @param string $msg
91
 */
92
function e($msg = '') {
93
    throw new \WebinoDevLib\Exception\DevelopmentException($msg);
94
}
95
96
/**
97
 * For testing purposes only
98
 *
99
 * User Acceptance Testing
100
 *
101
 * @return bool
102
 */
103
function isUat()
104
{
105
    return file_exists('tmp/common/uat.lock');
106
}
107