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
(1)
Code Injection enables an attacker to execute arbitrary code on the server.
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.
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.
$controllerClass
can contain request data and is used in code execution context(s) leading to a potential security vulnerability.1 path for user data to reach this point
filter_input_array(INPUT_SERVER)['REQUEST_URI']
seems to return tainted data, and$url
is assignedin src/Core/Request.php on line 25
$url
is passed through explode(), and$url
is assignedin src/Core/Request.php on line 33
$url[0]
is passed through trim(), andtrim($url[0])
is passed through trim(), and$url
is assignedin src/Core/Request.php on line 34
$url
is passed through explode(), and$partList
is assignedin src/Core/Request.php on line 36
$partList
is passed through implode(), and Request::$route is assignedin src/Core/Request.php on line 60
in src/Core/Request.php on line 115
$request->route()
is passed through preg_replace(), and$route
is assignedin src/Core/DefaultRoute.php on line 28
$route
is passed through str_replace(), and$controllerClass
is assignedin src/Core/DefaultRoute.php on line 32
General Strategies to prevent injection
In general, it is advisable to prevent any user-data to reach this point. This can be done by white-listing certain values:
For numeric data, we recommend to explicitly cast the data: