Rabilal vulnerabilities
We track 5 vulnerabilities in Rabilal products across 2 products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on July 8, 2026.
Latest Rabilal vulnerabilities
- 9.8 Critical severity
WP Learn Manager: Missing Authorization
The WP Learn Manager plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.1.8. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthentic
- 7.5 High severity
JS Help Desk – AI-Powered Support & Ticketing…: Improper Neutralization of Special Elements used in an SQL Command
The JS Help Desk – AI-Powered Support & Ticketing System plugin for WordPress is vulnerable to SQL Injection via the `multiformid` parameter in the `storeTickets()` function in all versions up to, and including, 3.0.4. This is due to the user-supplied `multifo
- 7.5 High severity
JS Help Desk – AI-Powered Support & Ticketing…: Improper Neutralization of Special Elements used in an SQL Command
The JS Help Desk – AI-Powered Support & Ticketing System plugin for WordPress is vulnerable to SQL Injection via the 'js-support-ticket-token-tkstatus' cookie in version 2.8.2 due to an incomplete fix for CVE-2023-50839 where a second sink was left with insuff
- 7.5 High severity
JS Help Desk – AI-Powered Support & Ticketing…: Exposure of Sensitive Information to an Unauthorized Actor
The JS Help Desk – The Ultimate Help Desk & Support Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.8.8 via the 'jssupportticketdata' directory. This makes it possible for unauthenticated atta
- 9.8 Critical severity
JS Help Desk – AI-Powered Support & Ticketing…: Improper Control of Generation of Code
The JS Help Desk – The Ultimate Help Desk & Support Plugin plugin for WordPress is vulnerable to PHP Code Injection leading to Remote Code Execution in all versions up to, and including, 2.8.6 via the 'storeTheme' function. This is due to a lack of sanitizatio