JS Help Desk – AI-Powered Support & Ticketing System <= 3.0.4 - Unauthenticated SQL Injection via 'multiformid' Parameter
Strategic Overview
- Status
- Patched in 3.0.5
- Affected Plugin
- JS Help Desk – AI-Powered Support & Ticketing System
- Affected Version
<= 3.0.4- CVSS
- 7.5High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2026-2511
At a glance
CVE-2026-2511 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the JS Help Desk WordPress plugin, affecting versions <= 3.0.4. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 3.0.5; sites on affected versions should update now. Disclosed March 2026, reported by Nabil Irawan.
Vulnerability Overview
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 `multiformid` value being passed to `esc_sql()` without enclosing the result in quotes in the SQL query, rendering the escaping ineffective against payloads that do not contain quote characters. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
JS Help Desk <= 3.0.4 carries this weakness at storeTickets(), and reaching it takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For JS Help Desk the fix is 3.0.5: builds <= 3.0.4 are affected, anything from 3.0.5 onward is not.
Remediation
Update to version 3.0.5, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: JS Help Desk 3.0.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in JS Help Desk – AI-Powered Support & Ticketing System
- 9.8CVE-2025-30901: JS Help Desk <= 2.9.2 Local File Inclusion
CVE-2025-30901 - 9.8CVE-2024-7094: JS Help Desk PHP Code Injection to RCE
CVE-2024-7094 - 9.8CVE-2022-46839: JS Help Desk <= 2.7.1 Arbitrary File Upload
CVE-2022-46839 - 9.1CVE-2025-30878: JS Help Desk <= 2.9.2 Arbitrary File Deletion
CVE-2025-30878 - 9.1CVE-2022-46838: JS Help Desk <= 2.7.1 Plugin Settings Update
CVE-2022-46838 - 8.8CVE-2026-56054: JS Help Desk Arbitrary File Deletion
CVE-2026-56054 - 8.8CVE-2018-21002: JS Help Desk – Best Help Desk & Support Plugin CSRF
CVE-2018-21002 - 7.5CVE-2025-30886: JS Help Desk <= 2.9.2 SQL Injection
CVE-2025-30886
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C