The WP Support Plus Responsive Ticket System WordPress plugin through 9.1.2 does not sign or verify its guest-session cookie, allowing unauthenticated attackers to forge it and impersonate any ticket owner (identified by email address) to read, reply to, and close that person's s...
Product
wordpress wp-support-plus-responsive-ticket-system vulnerabilities
15 published CVES affecting wordpress wp-support-plus-responsive-ticket-system, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 15
- Critical
- 6
- High
- 4
- Medium
- 5
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress wp-support-plus-responsive-ticket-system CVEs
Newest publication first
-
MediumCVSS 5.3 EPSS 0.32%
-
HighCVSS 8.6 EPSS 0.45%
The WP Support Plus Responsive Ticket System WordPress plugin through 9.1.2 does not sanitize user-supplied array keys before using them in a SQL statement, allowing unauthenticated users to perform SQL injection attacks.
-
HighCVSS 8.8 EPSS 0.51%
The WP Support Plus Responsive Ticket System WordPress plugin through 9.1.2 does not properly validate uploaded files, allowing unauthenticated users to upload files containing malicious JavaScript (such as HTML or SVG) to a publicly accessible location, leading to Stored Cross-S...
-
CVE-2019-15331 WP Support Plus Responsive Ticket System <= 9.1.1 - Stored Cross-Site Scripting
PublishedMediumCVSS 6.1 EPSS 0.91%The wp-support-plus-responsive-ticket-system plugin before 9.1.2 for WordPress has HTML injection.
-
CVE-2016-10930 Support Plus Responsive Ticket System < 7.1.0 - Insecure Direct Object Reference
PublishedCriticalCVSS 9.8 EPSS 2.0%The wp-support-plus-responsive-ticket-system plugin before 7.1.0 for WordPress has insecure direct object reference via a ticket number.
-
CriticalCVSS 9.8 EPSS 1.8%
The wp-support-plus-responsive-ticket-system plugin before 4.2 for WordPress has SQL injection.
-
MediumCVSS 5.3 EPSS 1.3%
The wp-support-plus-responsive-ticket-system plugin before 4.2 for WordPress has full path disclosure.
-
CriticalCVSS 9.8 EPSS 2.2%
The wp-support-plus-responsive-ticket-system plugin before 4.2 for WordPress has incorrect authentication.
-
CriticalCVSS 9.1 EPSS 2.5%
The wp-support-plus-responsive-ticket-system plugin before 4.2 for WordPress has directory traversal.
-
MediumCVSS 6.1 EPSS 0.91%
The wp-support-plus-responsive-ticket-system plugin before 4.1 for WordPress has JavaScript injection.
-
CVE-2019-7299 WP Support Plus Responsive Ticket System <= 9.1.1 - Stored Cross-Site Scripting
PublishedMediumCVSS 6.1 EPSS 1.7%A stored cross-site scripting (XSS) vulnerability in the submit_ticket.php module in the WP Support Plus Responsive Ticket System plugin 9.1.1 for WordPress allows remote attackers to inject arbitrary web script or HTML via the subject parameter in wp-content/plugins/wp-support-p...
-
CriticalCVSS 9.8 EPSS 2.1%
Pradeep Makone wordpress Support Plus Responsive Ticket System version 9.0.2 and earlier contains a SQL Injection vulnerability in the function to get tickets, the parameter email in cookie was injected that can result in filter the parameter. This attack appear to be exploitable...
-
HighCVSS 8.8
The WP Support Plus Responsive Ticket System plugin for WordPress is vulnerable to arbitrary file uploads in versions up to, and including 8.0.7. This is due to insufficient file type validation on the wpsp_upload_attachment AJAX action which makes it possible for authenticated a...
-
HighCVSS 8.8
The WP Support Plus Responsive Ticket System plugin for WordPress is vulnerable to generic SQL Injection via the "$_POST[‘cat_id’]" parameter in versions up to, and including, 7.1.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on...
-
CriticalCVSS 9.8
The WP Support Plus Responsive Ticket System plugin for WordPress is vulnerable to Authentication Bypass in versions up to, and including, 7.1.4. This is due to the plugin only requiring a valid email for the loginGuestFacebook AJAX action which is passed to the wp_set_auth_cooki...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.