Issues (685)

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.

src/Event/Logs.php (1 issue)

Labels
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
2
namespace App\Event;
3
4
use Cake\Event\Event;
5
use Cake\Event\EventListenerInterface;
6
use Cake\ORM\TableRegistry;
7
8
/**
9
 * Events descriptions.
10
 *
11
 * user.connection.manual.success : Triggered when the user login on the login page.
12
 * user.connection.manual.failed : Triggered when the user failed to login on the login page.
13
 * user.connection.auto : Triggered when the user is automated login with Cookies.
14
 * user.account.modify : Triggered when the user has modified his account.
15
 * user.email : Triggered when the user has changed his Email.
16
 * user.password.change : Triggered when the user has changed his password.
17
 * user.password.reset : Triggered when the user has asked a password reset.
18
 * user.password.reset.successful : Triggered when an user has successfully reset his password with the Email.
19
 * 2FA.enabled : Triggered when an user enbale the 2FA mode.
20
 * 2FA.disabled : Triggered when an user disable the 2FA mode.
21
 * 2FA.recovery_code.regenerate : Triggered when an user regenerate a new recovery code.
22
 * 2FA.recovery_code.used : Triggered when an user use his recovery code.
23
 */
24
25
class Logs implements EventListenerInterface
26
{
27
    /**
28
     * ImplementedEvents method.
29
     *
30
     * @return array
31
     */
32
    public function implementedEvents()
33
    {
34
        return [
35
            'Log.User' => 'userLog'
36
        ];
37
    }
38
39
    /**
40
     * An user has doing an important action, we log it.
41
     *
42
     * @param Event $event The event that was fired.
43
     *
44
     * @return bool
45
     */
46
    public function userLog(Event $event)
47
    {
48
        $this->UsersLogs = TableRegistry::get('UsersLogs');
0 ignored issues
show
The property UsersLogs does not exist. Did you maybe forget to declare it?

In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:

class MyClass { }

$x = new MyClass();
$x->foo = true;

Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:

class MyClass {
    public $foo;
}

$x = new MyClass();
$x->foo = true;
Loading history...
49
50
        $data = [
51
            'user_id' => $event->getData('user_id'),
52
            'username' => $event->getData('username'),
53
            'user_ip' => $event->getData('user_ip'),
54
            'user_agent' => $event->getData('user_agent'),
55
            'action' => $event->getData('action')
56
        ];
57
58
        $entity = $this->UsersLogs->newEntity($data);
59
        $this->UsersLogs->save($entity);
60
61
        return true;
62
    }
63
}
64