Issues in Workflows.php (master) - Issues in master - ryanwinchester/hubspot-php - Measure and Improve Code Quality continuously with Scrutinizer

Issues (318)

Security Analysis no request data

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/Resources/Workflows.php (9 issues)

Labels

Best Practice 9

Severity

Minor 9

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

<?php

namespace SevenShores\Hubspot\Resources;

class Workflows extends Resource
{
    /**
     * Get all workflows.
     *
     * @return \SevenShores\Hubspot\Http\Response
     */
    function all()

    {
        $endpoint = "https://api.hubapi.com/automation/v2/workflows";

        return $this->client->request('get', $endpoint);
    }

    /**
     * Get a specific workflow.
     *
     * @param int $id
     * @return \SevenShores\Hubspot\Http\Response
     */
    function getById($id)

    {
        $endpoint = "https://api.hubapi.com/automation/v2/workflows/{$id}";

        return $this->client->request('get', $endpoint);
    }

    /**
     * Enroll a contact in a workflow.
     *
     * @param int    $workflow_id
     * @param string $email
     * @return \SevenShores\Hubspot\Http\Response
     */
    function enrollContact($workflow_id, $email)

    {
        $endpoint = "https://api.hubapi.com/automation/v2/workflows/{$workflow_id}/enrollments/contacts/{$email}";

        return $this->client->request('post', $endpoint);
    }

    /**
     * Unenroll a contact from a workflow.
     *
     * @param int    $workflow_id
     * @param string $email
     * @return \SevenShores\Hubspot\Http\Response
     */
    function unenrollContact($workflow_id, $email)

    {
        $endpoint = "https://api.hubapi.com/automation/v2/workflows/{$workflow_id}/enrollments/contacts/{$email}";

        return $this->client->request('delete', $endpoint);
    }

    /**
     * Create a new workflow.
     *
     * @param array $workflow The workflow properties
     * @return \SevenShores\Hubspot\Http\Response
     */
    function create($workflow)

    {
        $endpoint = "https://api.hubapi.com/automation/v2/workflows";

        $options['json'] = $workflow;

        return $this->client->request('post', $endpoint, $options);
    }

    /**
     * Delete a workflow.
     *
     * @param int $id
     * @return \SevenShores\Hubspot\Http\Response
     */
    function delete($id)

    {
        $endpoint = "https://api.hubapi.com/automation/v2/workflows/{$id}";

        $queryString = build_query_string(['updatedAt' => time()]);

        return $this->client->request('delete', $endpoint, [], $queryString);
    }

    /**
     * Get current enrollments for a contact.
     *
     * @param int $contact_id
     * @return \SevenShores\Hubspot\Http\Response
     */
    function enrollmentsForContact($contact_id)

    {
        $endpoint = "https://api.hubapi.com/automation/v2/workflows/enrollments/contacts/{$contact_id}";

        return $this->client->request('get', $endpoint);
    }

    /**
     * Get past events for contact from a workflow.
     *
     * @param int   $workflow_id
     * @param int   $contact_id
     * @param array $params Optional parameters.
     * @return \SevenShores\Hubspot\Http\Response
     */
    function pastEventsForContact($workflow_id, $contact_id, $params = [])

    {
        $endpoint = " /automation/v2/workflows/{$workflow_id}/logevents/contacts/{$contact_id}/past";

        $queryString = build_query_string($params);

        return $this->client->request('get', $endpoint, [], $queryString);
    }

    /**
     * Get upcoming (scheduled) events for a contact in a workflow.
     *
     * @param int   $workflow_id
     * @param int   $contact_id
     * @param array $params
     * @return \SevenShores\Hubspot\Http\Response
     */
    function upcomingEventsForContact($workflow_id, $contact_id, $params = [])

    {
        $endpoint = "https://api.hubapi.com/automation/v2/workflows/{$workflow_id}/logevents/contacts/{$contact_id}/upcoming";

        $queryString = build_query_string($params);

        return $this->client->request('get', $endpoint, [], $queryString);
    }

}


1			<?php
2
3			namespace SevenShores\Hubspot\Resources;
4
5			class Workflows extends Resource
6			{
7			/**
8			* Get all workflows.
9			*
10			* @return \SevenShores\Hubspot\Http\Response
11			*/
12			function all()
			0 ignored issues – show Best Practice introduced 2016-06-04 02:40 UTC by Report Bug Copy Issue Report Show Similar Issues like this It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
13			{
14			$endpoint = "https://api.hubapi.com/automation/v2/workflows";
15
16			return $this->client->request('get', $endpoint);
17			}
18
19			/**
20			* Get a specific workflow.
21			*
22			* @param int $id
23			* @return \SevenShores\Hubspot\Http\Response
24			*/
25			function getById($id)
			0 ignored issues – show Best Practice introduced 2016-06-04 02:40 UTC by Report Bug Copy Issue Report Show Similar Issues like this It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
26			{
27			$endpoint = "https://api.hubapi.com/automation/v2/workflows/{$id}";
28
29			return $this->client->request('get', $endpoint);
30			}
31
32			/**
33			* Enroll a contact in a workflow.
34			*
35			* @param int $workflow_id
36			* @param string $email
37			* @return \SevenShores\Hubspot\Http\Response
38			*/
39			function enrollContact($workflow_id, $email)
			0 ignored issues – show Best Practice introduced 2016-06-04 02:40 UTC by Report Bug Copy Issue Report Show Similar Issues like this It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
40			{
41			$endpoint = "https://api.hubapi.com/automation/v2/workflows/{$workflow_id}/enrollments/contacts/{$email}";
42
43			return $this->client->request('post', $endpoint);
44			}
45
46			/**
47			* Unenroll a contact from a workflow.
48			*
49			* @param int $workflow_id
50			* @param string $email
51			* @return \SevenShores\Hubspot\Http\Response
52			*/
53			function unenrollContact($workflow_id, $email)
			0 ignored issues – show Best Practice introduced 2016-06-04 02:40 UTC by Report Bug Copy Issue Report Show Similar Issues like this It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
54			{
55			$endpoint = "https://api.hubapi.com/automation/v2/workflows/{$workflow_id}/enrollments/contacts/{$email}";
56
57			return $this->client->request('delete', $endpoint);
58			}
59
60			/**
61			* Create a new workflow.
62			*
63			* @param array $workflow The workflow properties
64			* @return \SevenShores\Hubspot\Http\Response
65			*/
66			function create($workflow)
			0 ignored issues – show Best Practice introduced 2016-06-04 02:40 UTC by Report Bug Copy Issue Report Show Similar Issues like this It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
67			{
68			$endpoint = "https://api.hubapi.com/automation/v2/workflows";
69
70			$options['json'] = $workflow;
71
72			return $this->client->request('post', $endpoint, $options);
73			}
74
75			/**
76			* Delete a workflow.
77			*
78			* @param int $id
79			* @return \SevenShores\Hubspot\Http\Response
80			*/
81			function delete($id)
			0 ignored issues – show Best Practice introduced 2016-06-04 02:40 UTC by Report Bug Copy Issue Report Show Similar Issues like this It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
82			{
83			$endpoint = "https://api.hubapi.com/automation/v2/workflows/{$id}";
84
85			$queryString = build_query_string(['updatedAt' => time()]);
86
87			return $this->client->request('delete', $endpoint, [], $queryString);
88			}
89
90			/**
91			* Get current enrollments for a contact.
92			*
93			* @param int $contact_id
94			* @return \SevenShores\Hubspot\Http\Response
95			*/
96			function enrollmentsForContact($contact_id)
			0 ignored issues – show Best Practice introduced 2016-06-04 02:40 UTC by Report Bug Copy Issue Report Show Similar Issues like this It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
97			{
98			$endpoint = "https://api.hubapi.com/automation/v2/workflows/enrollments/contacts/{$contact_id}";
99
100			return $this->client->request('get', $endpoint);
101			}
102
103			/**
104			* Get past events for contact from a workflow.
105			*
106			* @param int $workflow_id
107			* @param int $contact_id
108			* @param array $params Optional parameters.
109			* @return \SevenShores\Hubspot\Http\Response
110			*/
111			function pastEventsForContact($workflow_id, $contact_id, $params = [])
			0 ignored issues – show Best Practice introduced 2016-06-04 02:40 UTC by Report Bug Copy Issue Report Show Similar Issues like this It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
112			{
113			$endpoint = " /automation/v2/workflows/{$workflow_id}/logevents/contacts/{$contact_id}/past";
114
115			$queryString = build_query_string($params);
116
117			return $this->client->request('get', $endpoint, [], $queryString);
118			}
119
120			/**
121			* Get upcoming (scheduled) events for a contact in a workflow.
122			*
123			* @param int $workflow_id
124			* @param int $contact_id
125			* @param array $params
126			* @return \SevenShores\Hubspot\Http\Response
127			*/
128			function upcomingEventsForContact($workflow_id, $contact_id, $params = [])
			0 ignored issues – show Best Practice introduced 2016-06-04 02:40 UTC by Report Bug Copy Issue Report Show Similar Issues like this It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
129			{
130			$endpoint = "https://api.hubapi.com/automation/v2/workflows/{$workflow_id}/logevents/contacts/{$contact_id}/upcoming";
131
132			$queryString = build_query_string($params);
133
134			return $this->client->request('get', $endpoint, [], $queryString);
135			}
136
137			}
138

ryanwinchester / hubspot-php

Issues (318)

Security Analysis no request data

src/Resources/Workflows.php (9 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like