GitHub Access Token became invalid

It seems like the GitHub access token used for retrieving details about this repository from GitHub became invalid. This might prevent certain types of inspections from being run (in particular, everything related to pull requests).
Please ask an admin of your repository to re-new the access token on this website.

Issues (1881)

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.

includes/class-wpthumb-enhancements.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
/**
3
 * WPThumb Enhancements Class
4
 * Date: 7 Nov 2016
5
 *
6
 * Some themes include a filter to override the ORDER of the image editors to be used,
7
 * so that the GD library is used as a preference over the Imagick library.
8
 * This is acceptable, but WPThumb requires it's own overrides of the WP_Image_Editor_GD
9
 * and WP_Image_Editor_Imagick classes (set in wpthumb.php 'wpthumb_add_image_editors'
10
 * function). An example of this filter code is:
11
 *
12
 *   add_filter( 'wp_image_editors', 'change_graphic_lib' );
13
 *   function change_graphic_lib($array) {
14
 *     return array( 'WP_Image_Editor_GD', 'WP_Image_Editor_Imagick' );
15
 *   }
16
 *
17
 * The theme's filter runs after the WPThumb filter, so the override classes needed
18
 * by WPThumb are ignored. This stops WPThumb from working altogether. To get around
19
 * this we need to override the image editors later (priority 999) and "force" the
20
 * usage of the WPThumb override classes, while still preserving the order set by the
21
 * theme author, or server administrator.
22
 *
23
 * The hosting provider's decision to use GD over Imagick is usually due to a timeout
24
 * that occurs when large images are uploaded to the media library. The PHP setting
25
 * for memory on the server could be too low, and this causes Imagick to timeout.
26
 * Switching to GD usually fixes the problem, without needing to change memory limits.
27
 *
28
 */
29
if ( ! class_exists( 'FooGallery_WPThumb_Enhancements' ) ) {
30
31
    class FooGallery_WPThumb_Enhancements {
0 ignored issues
show
Coding Style Compatibility introduced by
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...
32
33
        function __construct() {
34
            add_filter( 'wp_image_editors', array( $this, 'override_image_editors' ), 999 );
35
        }
36
37
        /**
38
         * Overrides the editors to make sure the WPThumb editors are included
39
         *
40
         * @param $editors
41
         * @return array
42
         */
43
        function override_image_editors($editors) {
44
45
            $wpthumb_editors = array();
46
47
            //replace the default image editors with the WPThumb image editors.
48
            // also preserve the order so that certain hosts work as expected
49
            foreach ($editors as $editor) {
50
                switch ($editor) {
51
                    case 'WP_Image_Editor_Imagick':
52
                        $wpthumb_editors[] = 'WP_Thumb_Image_Editor_Imagick';
53
                        break;
54
                    case 'WP_Image_Editor_GD':
55
                        $wpthumb_editors[] = 'WP_Thumb_Image_Editor_GD';
56
                        break;
57
                    default:
58
                        $wpthumb_editors[] = $editor;
59
                }
60
            }
61
62
            //make sure we have a unique list of editors
63
            return array_unique( $wpthumb_editors );
64
        }
65
    }
66
}
67