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/bootstrap_cli.php (23 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...
This file is missing a doc comment.
Loading history...
2
declare(strict_types=1);
3
4
/**
0 ignored issues
show
The file-level docblock must follow the opening PHP tag in the file header
Loading history...
Inline doc block comments are not allowed; use "/* Comment */" or "// Comment" instead
Loading history...
Block comments must be started with /*
Loading history...
5
 * CakePHP(tm) : Rapid Development Framework (https://cakephp.org)
6
 * 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...
7
 *
8
 * Licensed under The MIT License
9
 * For full copyright and license information, please see the LICENSE.txt
10
 * Redistributions of files must retain the above copyright notice.
11
 *
12
 * @copyright     Copyright (c) Cake Software Foundation, Inc. (https://cakefoundation.org)
0 ignored issues
show
@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...
13
 * @link          https://cakephp.org CakePHP(tm) Project
0 ignored issues
show
The tag in position 2 should be the @license tag
Loading history...
Tag value indented incorrectly; expected 1 space but found 10
Loading history...
14
 * @since         3.0.0
0 ignored issues
show
Tag value indented incorrectly; expected 1 space but found 9
Loading history...
The tag in position 3 should be the @link tag
Loading history...
15
 * @license       https://opensource.org/licenses/mit-license.php MIT License
0 ignored issues
show
The tag in position 4 should be the @since tag
Loading history...
Tag value indented incorrectly; expected 1 space but found 7
Loading history...
16
 */
0 ignored issues
show
Missing @author tag in file comment
Loading history...
Missing @package tag in file comment
Loading history...
PHP version not specified
Loading history...
Missing @category tag in file comment
Loading history...
17
18
use Cake\Core\Configure;
19
20
/*
21
 * Additional bootstrapping and configuration for CLI environments should
22
 * be put here.
23
 */
24
25
// Set the fullBaseUrl to allow URLs to be generated in shell tasks.
26
// This is useful when sending email from shells.
27
//Configure::write('App.fullBaseUrl', php_uname('n'));
0 ignored issues
show
Inline comments must end in full-stops, exclamation marks, question marks, colons, or closing parentheses
Loading history...
Inline comments must end in full-stops, exclamation marks, or question marks
Loading history...
No space found before comment text; expected "// Configure::write('App.fullBaseUrl', php_uname('n'));" but found "//Configure::write('App.fullBaseUrl', php_uname('n'));"
Loading history...
There must be no blank line following an inline comment
Loading history...
28
29
// Set logs to different files so they don't have permission conflicts.
30
Configure::write('Log.debug.file', 'cli-debug');
31
Configure::write('Log.error.file', 'cli-error');
32