KB Support – Customer Support Ticket & Helpdesk Plugin, Knowledge Base Plugin
kb-support · plugin
Known security vulnerabilities for KB Support – Customer Support Ticket & Helpdesk Plugin, Knowledge Base Plugin. Find out in seconds which version runs on your site with WP Lens.
8 known vulnerabilities
4 exploitable without logging in · latest Apr 4, 2025
Closed on wordpress.org
Removed from the directory on Apr 3, 2025 · reason: security issue. 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
- High 8.8
CVE-2023-25983login required≤ 1.5.84
WordPress KB Support Plugin <= 1.5.84 is vulnerable to CSV Injection
- High 8.1
CVE-2024-8548subscriber+≤ 1.6.6
KB Support – WordPress Help Desk and Knowledge Base <= 1.6.6 - Missing Authorization to Authenticated (Subscriber+) Multiple Administrator Actions
- High 7.5
CVE-2024-13604unauthenticated≤ 1.7.4
KB Support – Customer Support Ticket & Helpdesk Plugin, Knowledge Base Plugin <= 1.7.4 - Unauthenticated Sensitive Information Exposure Through Unprotected Dire
- Medium 6.5
CVE-2024-8632unauthenticated≤ 1.6.6
KB Support – WordPress Help Desk and Knowledge Base <= 1.6.6 - Missing Authorization to Unauthenticated Ticket Reply Exposure
- Medium 6.5
CVE-2024-33589login required≤ 1.6.0
WordPress KB Support plugin <= 1.6.0 - Broken Access Control vulnerability
- Medium 6.1
CVE-2025-24741unauthenticated · needs a click≤ 1.6.7
WordPress KB Support plugin <= 1.6.7 - Open Redirection vulnerability
- Medium 6.1
CVE-2022-27852unauthenticated · needs a click≤ 1.5.5
WordPress KB Support plugin <= 1.5.5 - Multiple Unauth. Stored Cross-Site Scripting (XSS) vulnerabilities
- Medium 4.3
CVE-2023-37890subscriber+≤ 1.5.88
WordPress KB Support Plugin <= 1.5.88 is vulnerable to Broken Access Control
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).