WP Support Plus Responsive Ticket System
wp-support-plus-responsive-ticket-system · plugin
Known security vulnerabilities for WP Support Plus Responsive Ticket System. Find out in seconds which version runs on your site with WP Lens.
9 known vulnerabilities
5 critical · 9 exploitable without logging in · latest Aug 22, 2019
Closed on wordpress.org
Removed from the directory on Nov 23, 2022 · reason: author request. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- Critical 9.8
CVE-2016-10930unauthenticated
The wp-support-plus-responsive-ticket-system plugin before 7.1.0 for WordPress has insecure direct object reference via a ticket number.
- Critical 9.8
CVE-2014-10389unauthenticated
The wp-support-plus-responsive-ticket-system plugin before 4.2 for WordPress has incorrect authentication.
- Critical 9.8
CVE-2014-10387unauthenticated
The wp-support-plus-responsive-ticket-system plugin before 4.2 for WordPress has SQL injection.
- Critical 9.8
CVE-2018-1000131unauthenticated
Pradeep Makone wordpress Support Plus Responsive Ticket System version 9.0.2 and earlier contains a SQL Injection vulnerability in the funct
- Critical 9.1
CVE-2014-10390unauthenticated
The wp-support-plus-responsive-ticket-system plugin before 4.2 for WordPress has directory traversal.
- Medium 6.1
CVE-2019-15331unauthenticated · needs a click
The wp-support-plus-responsive-ticket-system plugin before 9.1.2 for WordPress has HTML injection.
- Medium 6.1
CVE-2014-10391unauthenticated · needs a click
The wp-support-plus-responsive-ticket-system plugin before 4.1 for WordPress has JavaScript injection.
- Medium 6.1
CVE-2019-7299unauthenticated · needs a click
A stored cross-site scripting (XSS) vulnerability in the submit_ticket.php module in the WP Support Plus Responsive Ticket System plugin 9.1
- Medium 5.3
CVE-2014-10388unauthenticated
The wp-support-plus-responsive-ticket-system plugin before 4.2 for WordPress has full path disclosure.
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).