Issues in EmailEvents.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/EmailEvents.php (4 issues)

Labels

Best Practice 4

Severity

Minor 4

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 EmailEvents extends Resource
{
    /**
     * Get campaign IDs for a portal.
     *
     * @param array $params Optional parameters
     * @return \SevenShores\Hubspot\Http\Response
     */
    function getCampaignIds($params = [])

    {
        $endpoint = "https://api.hubapi.com/email/public/v1/campaigns";

        $queryString = build_query_string($params);

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

    /**
     * Get campaign data for a given campaign.
     *
     * @param int $campaign_id
     * @param int $application_id
     * @return \SevenShores\Hubspot\Http\Response
     */
    function getCampaignById($campaign_id, $application_id)

    {
        $endpoint = "https://api.hubapi.com/email/public/v1/campaigns/{$campaign_id}";

        $queryString = build_query_string(['appId' => $application_id]);

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

    /**
     * Get email events for a campaign or recipient.
     *
     * @param array $params Optional parameters
     * @return \SevenShores\Hubspot\Http\Response
     */
    function all($params = [])

    {
        $endpoint = "https://api.hubapi.com/email/public/v1/events";

        $queryString = build_query_string($params);

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

    /**
     * Get event data for a specific event.
     *
     * @param int $id      The event ID
     * @param int $created Timestamp (milliseconds) when the event was created
     * @return \SevenShores\Hubspot\Http\Response
     */
    function getById($id, $created)

    {
        $endpoint = "https://api.hubapi.com/email/public/v1/events/{$created}/{$id}";

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


1			<?php
2
3			namespace SevenShores\Hubspot\Resources;
4
5			class EmailEvents extends Resource
6			{
7			/**
8			* Get campaign IDs for a portal.
9			*
10			* @param array $params Optional parameters
11			* @return \SevenShores\Hubspot\Http\Response
12			*/
13			function getCampaignIds($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...
14			{
15			$endpoint = "https://api.hubapi.com/email/public/v1/campaigns";
16
17			$queryString = build_query_string($params);
18
19			return $this->client->request('get', $endpoint, [], $queryString);
20			}
21
22			/**
23			* Get campaign data for a given campaign.
24			*
25			* @param int $campaign_id
26			* @param int $application_id
27			* @return \SevenShores\Hubspot\Http\Response
28			*/
29			function getCampaignById($campaign_id, $application_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...
30			{
31			$endpoint = "https://api.hubapi.com/email/public/v1/campaigns/{$campaign_id}";
32
33			$queryString = build_query_string(['appId' => $application_id]);
34
35			return $this->client->request('get', $endpoint, [], $queryString);
36			}
37
38			/**
39			* Get email events for a campaign or recipient.
40			*
41			* @param array $params Optional parameters
42			* @return \SevenShores\Hubspot\Http\Response
43			*/
44			function all($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...
45			{
46			$endpoint = "https://api.hubapi.com/email/public/v1/events";
47
48			$queryString = build_query_string($params);
49
50			return $this->client->request('get', $endpoint, [], $queryString);
51			}
52
53			/**
54			* Get event data for a specific event.
55			*
56			* @param int $id The event ID
57			* @param int $created Timestamp (milliseconds) when the event was created
58			* @return \SevenShores\Hubspot\Http\Response
59			*/
60			function getById($id, $created)
			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...
61			{
62			$endpoint = "https://api.hubapi.com/email/public/v1/events/{$created}/{$id}";
63
64			return $this->client->request('get', $endpoint);
65			}
66			}
67

ryanwinchester / hubspot-php

Issues (318)

Security Analysis no request data

src/Resources/EmailEvents.php (4 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like