Issues in deprecated.php (master) - Issues in master - humanmade/backupwordpress - Measure and Improve Code Quality continuously with Scrutinizer

Issues (217)

Security Analysis no vulnerabilities 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.

classes/deprecated.php (10 issues)

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

<?php


/**
 * An abstract service class, individual services should
 * extend this class
 */
abstract class HMBKP_Service {}
namespace YourVendor;

class YourClass { }

/**
 * A singleton to handle the registering, de-registering
 * and storage of services
 */
class HMBKP_Services {
namespace YourVendor;

class YourClass { }

	/**
	 * Store the current instance
	 *
	 * @access private
	 * @var object HMBKP_Services
	 * @static
	 */
	private static $instance;

	/**
	 * The array of services
	 *
	 * Should be of the format array( __FILE__ => __CLASS__ );
	 *
	 * @access private
	 * @var  array
	 * @static
	 */
	private $services = array();


	/**
	 * The current schedule object
	 *
	 * @access private
	 * @var object HMBKP_Scheduled_Backup
	 */
	private $schedule;


	/**
	 * Get the current instance
	 *
	 * @access public
	 * @static
	 */
	public static function instance() {

		if ( ! isset( self::$instance ) )
			self::$instance = new HMBKP_Services;

		return self::$instance;

	}

	/**
	 * Register a new service
	 *
	 * @param $filepath
	 * @param $classname
	 * @return bool|WP_Error

	 */
	public static function register( $filepath, $classname ) {


		_deprecated_function( __METHOD__, '3.1.2' );
	}

	/**
	 * Instantiate the individual service classes
	 *
	 * @param string $classname
	 *
	 * @return array An array of instantiated classes

	 */
	private static function instantiate( $classname ) {


		if ( ! class_exists( $classname ) )
			return new \WP_Error( 'hmbkp_invalid_type_error', sprintf( __( 'Argument 1 for %s must be a valid class', 'backupwordpress' ) ), __METHOD__ );

		/**
		 * @var HMBKP_Service
		 */
		$class = new $classname( self::instance()->schedule );

		return $class;

	}

}


1		<?php
2
3
4		/**
5		* An abstract service class, individual services should
6		* extend this class
7		*/
8		abstract class HMBKP_Service {}
		0 ignored issues – show Coding Style Compatibility introduced 2015-11-21 01:52 UTC by Report Bug Copy Issue Report Show Similar Issues like this PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions. You can fix this by adding a namespace to your class: namespace YourVendor; class YourClass { } When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries. Loading history...
9
10		/**
11		* A singleton to handle the registering, de-registering
12		* and storage of services
13		*/
14		class HMBKP_Services {
		0 ignored issues – show Coding Style Compatibility introduced 2015-11-21 01:52 UTC by Report Bug Copy Issue Report Show Similar Issues like this PSR1 recommends that each class should be in its own file to aid autoloaders. Having each class in a dedicated file usually plays nice with PSR autoloaders and is therefore a well established practice. If you use other autoloaders, you might not want to follow this rule. Loading history... Coding Style Compatibility introduced 2015-11-21 01:52 UTC by Report Bug Copy Issue Report Show Similar Issues like this PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions. You can fix this by adding a namespace to your class: namespace YourVendor; class YourClass { } When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries. Loading history...
15
16		/**
17		* Store the current instance
18		*
19		* @access private
20		* @var object HMBKP_Services
21		* @static
22		*/
23		private static $instance;
24
25		/**
26		* The array of services
27		*
28		* Should be of the format array( __FILE__ => __CLASS__ );
29		*
30		* @access private
31		* @var array
32		* @static
33		*/
34		private $services = array();
		0 ignored issues – show Unused Code introduced 2015-11-21 01:52 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `$services` is not used and could be removed. This check marks private properties in classes that are never used. Those properties can be removed. Loading history...
35
36		/**
37		* The current schedule object
38		*
39		* @access private
40		* @var object HMBKP_Scheduled_Backup
41		*/
42		private $schedule;
		0 ignored issues – show Unused Code introduced 2015-11-21 01:52 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `$schedule` is not used and could be removed. This check marks private properties in classes that are never used. Those properties can be removed. Loading history...
43
44		/**
45		* Get the current instance
46		*
47		* @access public
48		* @static
49		*/
50		public static function instance() {
51
52		if ( ! isset( self::$instance ) )
53		self::$instance = new HMBKP_Services;
54
55		return self::$instance;
56
57		}
58
59		/**
60		* Register a new service
61		*
62		* @param $filepath
63		* @param $classname
64		* @return bool\|WP_Error
		0 ignored issues – show Documentation introduced 2015-11-21 01:52 UTC by Report Bug Copy Issue Report Show Similar Issues like this Should the return type not be `boolean\|WP_Error\|null`? This check compares the return type specified in the `@return` annotation of a function or method doc comment with the types returned by the function and raises an issue if they mismatch. Loading history...
65		*/
66		public static function register( $filepath, $classname ) {
		0 ignored issues – show Unused Code introduced 2015-11-21 01:52 UTC by Report Bug Copy Issue Report Show Similar Issues like this The parameter `$filepath` is not used and could be removed. This check looks from parameters that have been defined for a function or method, but which are not used in the method body. Loading history... Unused Code introduced 2015-11-21 01:52 UTC by Report Bug Copy Issue Report Show Similar Issues like this The parameter `$classname` is not used and could be removed. This check looks from parameters that have been defined for a function or method, but which are not used in the method body. Loading history...
67
68		_deprecated_function( __METHOD__, '3.1.2' );
69		}
70
71		/**
72		* Instantiate the individual service classes
73		*
74		* @param string $classname
75		*
76		* @return array An array of instantiated classes
		0 ignored issues – show Documentation introduced 2015-11-21 01:52 UTC by Report Bug Copy Issue Report Show Similar Issues like this Should the return type not be `object`? This check compares the return type specified in the `@return` annotation of a function or method doc comment with the types returned by the function and raises an issue if they mismatch. Loading history...
77		*/
78	View Code Duplication	private static function instantiate( $classname ) {
		0 ignored issues – show Unused Code introduced 2015-11-21 01:52 UTC by Report Bug Copy Issue Report Show Similar Issues like this This method is not used, and could be removed. Loading history...
79
80		if ( ! class_exists( $classname ) )
81		return new \WP_Error( 'hmbkp_invalid_type_error', sprintf( __( 'Argument 1 for %s must be a valid class', 'backupwordpress' ) ), __METHOD__ );
82
83		/**
84		* @var HMBKP_Service
85		*/
86		$class = new $classname( self::instance()->schedule );
87
88		return $class;
89
90		}
91
92		}
93

GitHub Access Token became invalid

Issues (217)

Security Analysis no vulnerabilities found

classes/deprecated.php (10 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

humanmade / backupwordpress

GitHub Access Token became invalid

Issues (217)

Security Analysis no vulnerabilities found

classes/deprecated.php (10 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like