Issues (4388)

Security Analysis    no vulnerabilities found

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.

config/paths.php (40 issues)

1
<?php
0 ignored issues
show
The PHP open tag does not have a corresponding PHP close tag
Loading history...
Header blocks must be separated by a single blank line
Loading history...
2
/**
3
 * CakePHP(tm) : Rapid Development Framework (https://cakephp.org)
0 ignored issues
show
The second line in the file doc comment must be "@file"
Loading history...
4
 * Copyright (c) Cake Software Foundation, Inc. (https://cakefoundation.org)
0 ignored issues
show
Doc comment short description must be on a single line, further text should be a separate paragraph
Loading history...
5
 *
6
 * Licensed under The MIT License
7
 * Redistributions of files must retain the above copyright notice.
8
 *
9
 * @copyright     Copyright (c) Cake Software Foundation, Inc. (https://cakefoundation.org)
0 ignored issues
show
Coding Style Documentation introduced by
Expected "xxxx-xxxx Squiz Pty Ltd (ABN 77 084 670 600)" for copyright declaration
Loading history...
The tag in position 1 should be the @package tag
Loading history...
@copyright tag must contain a year and the name of the copyright holder
Loading history...
Tag value indented incorrectly; expected 1 space but found 5
Loading history...
10
 * @link          https://cakephp.org CakePHP(tm) Project
0 ignored issues
show
Tag value indented incorrectly; expected 1 space but found 10
Loading history...
The tag in position 2 should be the @subpackage tag
Loading history...
The tag in position 2 should be the @license tag
Loading history...
11
 * @since         3.0.0
0 ignored issues
show
The tag in position 3 should be the @author tag
Loading history...
The tag in position 3 should be the @link tag
Loading history...
Tag value indented incorrectly; expected 1 space but found 9
Loading history...
12
 * @license       MIT License (https://opensource.org/licenses/mit-license.php)
0 ignored issues
show
Tag value indented incorrectly; expected 1 space but found 7
Loading history...
The tag in position 4 should be the @since tag
Loading history...
The tag in position 4 should be the @copyright tag
Loading history...
13
 */
0 ignored issues
show
Coding Style Documentation introduced by
Missing @package tag in file comment
Loading history...
PHP version not specified
Loading history...
Coding Style Documentation introduced by
Missing @subpackage tag in file comment
Loading history...
Coding Style Documentation introduced by
Missing @author tag in file comment
Loading history...
Missing @category tag in file comment
Loading history...
14
15
/*
16
 * Use the DS to separate the directories in other defines
17
 */
0 ignored issues
show
Empty line required after block comment
Loading history...
18
if (!defined('DS')) {
0 ignored issues
show
Expected 1 space(s) after NOT operator; 0 found
Loading history...
19
    define('DS', DIRECTORY_SEPARATOR);
20
}
21
22
/*
23
 * These defines should only be edited if you have cake installed in
24
 * a directory layout other than the way it is distributed.
25
 * When using custom settings be sure to use the DS and do not add a trailing DS.
0 ignored issues
show
Line exceeds 80 characters; contains 81 characters
Loading history...
26
 */
27
28
/*
29
 * The full path to the directory which holds "src", WITHOUT a trailing DS.
30
 */
0 ignored issues
show
Empty line required after block comment
Loading history...
31
define('ROOT', dirname(__DIR__));
32
33
/*
34
 * The actual directory name for the application directory. Normally
35
 * named 'src'.
36
 */
0 ignored issues
show
Empty line required after block comment
Loading history...
37
define('APP_DIR', 'src');
38
39
/*
40
 * Path to the application's directory.
41
 */
0 ignored issues
show
Empty line required after block comment
Loading history...
42
define('APP', ROOT . DS . APP_DIR . DS);
43
44
/*
45
 * Path to the config directory.
46
 */
0 ignored issues
show
Empty line required after block comment
Loading history...
47
define('CONFIG', ROOT . DS . 'config' . DS);
48
49
/*
50
 * File path to the webroot directory.
51
 *
52
 * To derive your webroot from your webserver change this to:
53
 *
54
 * `define('WWW_ROOT', rtrim($_SERVER['DOCUMENT_ROOT'], DS) . DS);`
55
 */
0 ignored issues
show
Empty line required after block comment
Loading history...
56
define('WWW_ROOT', ROOT . DS . 'webroot' . DS);
57
58
/*
59
 * Path to the tests directory.
60
 */
0 ignored issues
show
Empty line required after block comment
Loading history...
61
define('TESTS', ROOT . DS . 'tests' . DS);
62
63
/*
64
 * Path to the temporary files directory.
65
 */
0 ignored issues
show
Empty line required after block comment
Loading history...
66
define('TMP', ROOT . DS . 'tmp' . DS);
67
68
/*
69
 * Path to the logs directory.
70
 */
0 ignored issues
show
Empty line required after block comment
Loading history...
71
define('LOGS', ROOT . DS . 'logs' . DS);
72
73
/*
74
 * Path to the cache files directory. It can be shared between hosts in a multi-server setup.
0 ignored issues
show
Line exceeds 80 characters; contains 93 characters
Loading history...
75
 */
0 ignored issues
show
Empty line required after block comment
Loading history...
76
define('CACHE', TMP . 'cache' . DS);
77
78
/**
0 ignored issues
show
Inline doc block comments are not allowed; use "/* Comment */" or "// Comment" instead
Loading history...
Block comments must be started with /*
Loading history...
79
 * Path to the resources directory.
80
 */
81
define('RESOURCES', ROOT . DS . 'resources' . DS);
82
83
/**
0 ignored issues
show
Inline doc block comments are not allowed; use "/* Comment */" or "// Comment" instead
Loading history...
Block comments must be started with /*
Loading history...
84
 * The absolute path to the "cake" directory, WITHOUT a trailing DS.
85
 *
86
 * CakePHP should always be installed with composer, so look there.
87
 */
88
define('CAKE_CORE_INCLUDE_PATH', ROOT . DS . 'vendor' . DS . 'cakephp' . DS . 'cakephp');
89
90
/*
91
 * Path to the cake directory.
92
 */
0 ignored issues
show
Empty line required after block comment
Loading history...
93
define('CORE_PATH', CAKE_CORE_INCLUDE_PATH . DS);
94
define('CAKE', CORE_PATH . 'src' . DS);
95