Issues (1240)

Security Analysis    not enabled

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.

system/controllers/template.php (4 issues)

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 defined('SYSPATH') or die('No direct access allowed.');
2
/**
3
 * Allows a template to be automatically loaded and displayed. Display can be
4
 * dynamically turned off in the controller methods, and the template file
5
 * can be overloaded.
6
 *
7
 * To use it, declare your controller to extend this class:
8
 * `class Your_Controller extends Template_Controller`
9
 *
10
 * $Id: template.php 3769 2008-12-15 00:48:56Z zombor $
11
 *
12
 * @package    Core
13
 * @author     Kohana Team
14
 * @copyright  (c) 2007-2008 Kohana Team
15
 * @license    http://kohanaphp.com/license.html
16
 */
17
abstract class Template_Controller extends Controller
18
{
19
20
    // Template view name
21
    public $template = 'template';
22
23
    // Default to do auto-rendering
24
    public $auto_render = true;
25
26
    /**
27
     * Template loading and setup routine.
28
     */
29
    public function __construct()
30
    {
31
        parent::__construct();
32
33
        // Load the template
34
        $this->template = new View($this->template);
0 ignored issues
show
Documentation Bug introduced by
It seems like new \View($this->template) of type object<View> is incompatible with the declared type string of property $template.

Our type inference engine has found an assignment to a property that is incompatible with the declared type of that property.

Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property..

Loading history...
35
36
        if ($this->auto_render == true) {
0 ignored issues
show
Coding Style Best Practice introduced by
It seems like you are loosely comparing two booleans. Considering using the strict comparison === instead.

When comparing two booleans, it is generally considered safer to use the strict comparison operator.

Loading history...
37
            // Render the template immediately after the controller method
38
            Event::add('system.post_controller', array($this, '_render'));
39
        }
40
    }
41
42
    /**
43
     * Render the loaded template.
44
     */
45
    public function _render()
46
    {
47
        if ($this->auto_render == true) {
0 ignored issues
show
Coding Style Best Practice introduced by
It seems like you are loosely comparing two booleans. Considering using the strict comparison === instead.

When comparing two booleans, it is generally considered safer to use the strict comparison operator.

Loading history...
48
            // Render the template when the class is destroyed
49
            $this->template->render(true);
0 ignored issues
show
The method render cannot be called on $this->template (of type string).

Methods can only be called on objects. This check looks for methods being called on variables that have been inferred to never be objects.

Loading history...
50
        }
51
    }
52
} // End Template_Controller
53