Issues in CacheAjax.php (master) - Issues in master - pH7Software/pH7-Social-Dating-CMS - Measure and Improve Code Quality continuously with Scrutinizer

Issues (3445)

Security Analysis not enabled

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.

system/modules/admin123/assets/ajax/CacheAjax.php (3 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

/**
 * @author         Pierre-Henry Soria <[email protected]>
 * @copyright      (c) 2012-2019, Pierre-Henry Soria. All Rights Reserved.
 * @license        GNU General Public License; See PH7.LICENSE.txt and PH7.COPYRIGHT.txt in the root directory.
 * @package        PH7 / App / System / Module / Admin / Asset / Ajax
 */

namespace PH7;

defined('PH7') or exit('Restricted access');

use PH7\Framework\Cache\Cache;
use PH7\Framework\Core\Kernel;
use PH7\Framework\Http\Http;
use PH7\Framework\Layout\Gzip\Gzip;
use PH7\Framework\Layout\Tpl\Engine\PH7Tpl\PH7Tpl;
use PH7\Framework\Security\CSRF\Token;
use Teapot\StatusCode;

class CacheAjax extends Kernel
{
    public function __construct()
    {
        parent::__construct();

        if (!(new Token)->check('cache')) {
            exit(jsonMsg(0, Form::errorTokenMsg()));

        }

        $this->clearCache();
    }

    private function clearCache()
    {
        switch ($this->httpRequest->post('type')) {
            case 'general':
                $this->file->deleteDir(PH7_PATH_CACHE . Cache::CACHE_DIR);
                $this->clearBrowserCache();
                break;

            case 'tpl_compile':
                $this->file->deleteDir(PH7_PATH_CACHE . PH7Tpl::COMPILE_DIR);
                $this->clearBrowserCache();
                break;

            case 'tpl_html':
                $this->file->deleteDir(PH7_PATH_CACHE . PH7Tpl::CACHE_DIR);
                $this->clearBrowserCache();
                break;

            case 'static':
                $this->file->deleteDir(PH7_PATH_CACHE . Gzip::CACHE_DIR);
                $this->clearBrowserCache();
                break;

            default:
                Http::setHeadersByCode(StatusCode::BAD_REQUEST);
                exit('Bad Request Error');

        }

        echo jsonMsg(1, t('The cache has been cleared.'));
    }

    /**
     * Clear the Web browser's cache.
     *
     * @return void
     */
    private function clearBrowserCache()
    {
        $this->browser->noCache();
    }
}

// Only for Admins
if (Admin::auth()) {
    new CacheAjax;
}


1			<?php
			0 ignored issues – show Coding Style Compatibility introduced 2017-02-18 20:34 UTC by Report Bug Copy Issue Report Show Similar Issues like this For compatibility and reusability of your code, PSR1 recommends that a file should introduce either new symbols (like classes, functions, etc.) or have side-effects (like outputting something, or including other files), but not both at the same time. The first symbol is defined on line 21 and the first side effect is on line 11. The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file. The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place. To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1. Loading history...
2			/**
3			* @author Pierre-Henry Soria <[email protected]>
4			* @copyright (c) 2012-2019, Pierre-Henry Soria. All Rights Reserved.
5			* @license GNU General Public License; See PH7.LICENSE.txt and PH7.COPYRIGHT.txt in the root directory.
6			* @package PH7 / App / System / Module / Admin / Asset / Ajax
7			*/
8
9			namespace PH7;
10
11			defined('PH7') or exit('Restricted access');
12
13			use PH7\Framework\Cache\Cache;
14			use PH7\Framework\Core\Kernel;
15			use PH7\Framework\Http\Http;
16			use PH7\Framework\Layout\Gzip\Gzip;
17			use PH7\Framework\Layout\Tpl\Engine\PH7Tpl\PH7Tpl;
18			use PH7\Framework\Security\CSRF\Token;
19			use Teapot\StatusCode;
20
21			class CacheAjax extends Kernel
22			{
23			public function __construct()
24			{
25			parent::__construct();
26
27			if (!(new Token)->check('cache')) {
28			exit(jsonMsg(0, Form::errorTokenMsg()));
			0 ignored issues – show Coding Style Compatibility introduced 2015-12-19 18:10 UTC by Report Bug Copy Issue Report Show Similar Issues like this The method `__construct()` contains an exit expression. An exit expression should only be used in rare cases. For example, if you write a short command line script. In most cases however, using an `exit` expression makes the code untestable and often causes incompatibilities with other libraries. Thus, unless you are absolutely sure it is required here, we recommend to refactor your code to avoid its usage. Loading history...
29			}
30
31			$this->clearCache();
32			}
33
34			private function clearCache()
35			{
36			switch ($this->httpRequest->post('type')) {
37			case 'general':
38			$this->file->deleteDir(PH7_PATH_CACHE . Cache::CACHE_DIR);
39			$this->clearBrowserCache();
40			break;
41
42			case 'tpl_compile':
43			$this->file->deleteDir(PH7_PATH_CACHE . PH7Tpl::COMPILE_DIR);
44			$this->clearBrowserCache();
45			break;
46
47			case 'tpl_html':
48			$this->file->deleteDir(PH7_PATH_CACHE . PH7Tpl::CACHE_DIR);
49			$this->clearBrowserCache();
50			break;
51
52			case 'static':
53			$this->file->deleteDir(PH7_PATH_CACHE . Gzip::CACHE_DIR);
54			$this->clearBrowserCache();
55			break;
56
57			default:
58			Http::setHeadersByCode(StatusCode::BAD_REQUEST);
59			exit('Bad Request Error');
			0 ignored issues – show Coding Style Compatibility introduced 2015-12-19 18:10 UTC by Report Bug Copy Issue Report Show Similar Issues like this The method `clearCache()` contains an exit expression. An exit expression should only be used in rare cases. For example, if you write a short command line script. In most cases however, using an `exit` expression makes the code untestable and often causes incompatibilities with other libraries. Thus, unless you are absolutely sure it is required here, we recommend to refactor your code to avoid its usage. Loading history...
60			}
61
62			echo jsonMsg(1, t('The cache has been cleared.'));
63			}
64
65			/**
66			* Clear the Web browser's cache.
67			*
68			* @return void
69			*/
70			private function clearBrowserCache()
71			{
72			$this->browser->noCache();
73			}
74			}
75
76			// Only for Admins
77			if (Admin::auth()) {
78			new CacheAjax;
79			}
80

pH7Software / pH7-Social-Dating-CMS

Issues (3445)

Security Analysis not enabled

system/modules/admin123/assets/ajax/CacheAjax.php (3 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like