Pivotx
Sign in to watchby Pivotx
CVEs (15)
| CVE | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2017-8402 | Hig | 0.57 | 8.8 | 0.01 | May 31, 2017 | PivotX 2.3.11 allows remote authenticated users to execute arbitrary PHP code via vectors involving an upload of a .htaccess file. | |
| CVE-2017-7570 | Hig | 0.57 | 8.8 | 0.01 | Apr 7, 2017 | PivotX 2.3.11 allows remote authenticated Advanced users to execute arbitrary PHP code by performing an upload with a safe file extension (such as .jpg) and then invoking the duplicate function to change to the .php extension. | |
| CVE-2017-14958 | Hig | 0.47 | 7.2 | 0.01 | Oct 2, 2017 | lib.php in PivotX 2.3.11 does not properly block uploads of dangerous file types by admin users, which allows remote PHP code execution via an upload of a .php file. | |
| CVE-2017-9332 | Med | 0.40 | 6.1 | 0.00 | Jun 6, 2017 | The smarty_self function in modules/module_smarty.php in PivotX 2.3.11 mishandles the URI, allowing XSS via vectors involving quotes in the self Smarty tag. | |
| CVE-2011-0773 | 0.04 | — | 0.09 | Feb 4, 2011 | Cross-site scripting (XSS) vulnerability in pivotx/modules/module_image.php in PivotX before 2.2.3 allows remote attackers to inject arbitrary web script or HTML via the image parameter. | ||
| CVE-2011-0772 | 0.04 | — | 0.10 | Feb 4, 2011 | Multiple cross-site scripting (XSS) vulnerabilities in PivotX 2.2.0, and possibly other versions before 2.2.2, allow remote attackers to inject arbitrary web script or HTML via the (1) color parameter to includes/blogroll.php or (2) src parameter to includes/timwrapper.php. | ||
| CVE-2012-2274 | 0.03 | — | 0.01 | Aug 13, 2012 | Cross-site scripting (XSS) vulnerability in pivotx/ajaxhelper.php in PivotX 2.3.2 and earlier allows remote attackers to inject arbitrary web script or HTML via the file parameter. | ||
| CVE-2015-5458 | 0.00 | — | 0.01 | Jul 8, 2015 | Session fixation vulnerability in fileupload.php in PivotX before 2.3.11 allows remote attackers to hijack web sessions via the sess parameter. | ||
| CVE-2015-5457 | 0.00 | — | 0.03 | Jul 8, 2015 | PivotX before 2.3.11 does not validate the new file extension when renaming a file with multiple extensions, which allows remote attackers to execute arbitrary code by uploading a crafted file, as demonstrated by a file named foo.php.php. | ||
| CVE-2015-5456 | 0.00 | — | 0.00 | Jul 8, 2015 | Cross-site scripting (XSS) vulnerability in the form method in modules/formclass.php in PivotX before 2.3.11 allows remote attackers to inject arbitrary web script or HTML via the PATH_INFO, related to the "PHP_SELF" variable and form actions. | ||
| CVE-2014-0342 | 0.00 | — | 0.02 | Apr 15, 2014 | Multiple unrestricted file upload vulnerabilities in fileupload.php in PivotX before 2.3.9 allow remote authenticated users to execute arbitrary PHP code by uploading a file with a (1) .php or (2) .php# extension, and then accessing it via unspecified vectors. | ||
| CVE-2014-0341 | 0.00 | — | 0.01 | Apr 15, 2014 | Multiple cross-site scripting (XSS) vulnerabilities in PivotX before 2.3.9 allow remote authenticated users to inject arbitrary web script or HTML via the title field to (1) templates_internal/pages.tpl, (2) templates_internal/home.tpl, or (3) templates_internal/entries.tpl; (4) an event field to objects.php; or the (5) email or (6) nickname field to pages.php, related to templates_internal/users.tpl. | ||
| CVE-2011-1035 | 0.00 | — | 0.03 | Feb 19, 2011 | The password reset in PivotX before 2.2.4 allows remote attackers to modify the passwords of arbitrary users via unspecified vectors. | ||
| CVE-2011-0775 | 0.00 | — | 0.00 | Feb 4, 2011 | pivotx/modules/module_image.php in PivotX 2.2.2 allows remote attackers to obtain sensitive information via a non-existent file in the image parameter, which reveals the installation path in an error message. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information. | ||
| CVE-2011-0774 | 0.00 | — | 0.00 | Feb 4, 2011 | PivotX before 2.2.2 allows remote attackers to obtain sensitive information via a direct request to (1) includes/ping.php and (2) includes/spamping.php, which reveals the installation path in an error message. |