Issues (125)

Security Analysis    no request data  

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.

src/svg/XMLDocumentInterface.php (1 issue)

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
2
namespace nstdio\svg;
3
4
5
interface XMLDocumentInterface
6
{
7
    /**
8
     * @return XMLDocumentInterface|\DOMElement|\DOMDocument
9
     */
10
    public function getElement();
11
12
    /**
13
     * @param mixed $value The text value of node.
14
     */
15
    public function setNodeValue($value);
16
17
    /**
18
     * @return string The text value of node.
19
     */
20
    public function getNodeValue();
21
22
    /**
23
     * @param array $except Returned array will not contain attributes specified in this array.
24
     *
25
     * @return array Associative array where the keys are the name of the attribute node.
26
     */
27
    public function attributes(array $except);
28
29
    /**
30
     * @param string $name
31
     * @param mixed $value
32
     * @return void
33
     */
34
    public function setAttribute($name, $value = null);
35
36
    /**
37
     * @param string $name Attribute name.
38
     * @return string Attribute value.
39
     */
40
    public function getAttribute($name);
41
42
    /**
43
     * @param $namespaceURI
44
     * @param $qualifiedName
45
     * @param $value
46
     * @return string
47
     */
48
    public function setAttributeNS($namespaceURI, $qualifiedName, $value);
49
50
    /**
51
     * @param $namespaceURI
52
     * @param $localName
53
     * @return mixed
54
     */
55
    public function getAttributeNS($namespaceURI, $localName);
56
57
    /**
58
     * @param XMLDocumentInterface $newNode
59
     * @return void
60
     */
61
    public function appendChild(XMLDocumentInterface $newNode);
62
63
    /**
64
     * @param string $name
65
     * @param mixed $value
66
     *
67
     * @return XMLDocumentInterface A new element.
68
     */
69
    public function createElement($name, $value = null);
70
71
    /**
72
     * @param string $namespaceURI
73
     * @param string $qualifiedName
74
     * @param string $value
0 ignored issues
show
Should the type for parameter $value not be string|null?

This check looks for @param annotations where the type inferred by our type inference engine differs from the declared type.

It makes a suggestion as to what type it considers more descriptive.

Most often this is a case of a parameter that can be null in addition to its declared types.

Loading history...
75
     * @return mixed
76
     */
77
    public function createElementNS($namespaceURI, $qualifiedName, $value = null);
78
79
    /**
80
     * @param XMLDocumentInterface $child The element to remove.
81
     *
82
     * @return mixed
83
     */
84
    public function removeNode(XMLDocumentInterface $child);
85
86
    /**
87
     * @return string
88
     */
89
    public function saveHTML();
90
91
    /**
92
     * @param bool $formatOutput Whether formatou
93
     *
94
     * @return string
95
     */
96
    public function saveXML($formatOutput);
97
98
    /**
99
     * @return bool
100
     */
101
    public static function isLoaded();
102
103
}