EUVD-2026-43122
GHSA-jvc5-5493-8v66
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Network AJAX endpoint requires only Subscriber-level nonce; confidentiality impact is high (full DB read); no write or availability path confirmed.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
Lifecycle Timeline
2DescriptionCVE.org
The Majestic Support - The Leading-Edge Help Desk & Customer Support Plugin plugin for WordPress is vulnerable to generic SQL Injection via the 'val' parameter in all versions up to, and including, 1.1.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. 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. Exploitation requires a valid 'get-smart-reply' nonce, which any Subscriber-level user can obtain by creating a ticket via the public frontend and visiting the resulting ticket detail page, making this effectively exploitable by any authenticated user.
AnalysisAI
SQL injection in the Majestic Support WordPress help desk plugin (versions up to and including 1.1.9) allows any authenticated WordPress user to extract sensitive data from the site's database by appending arbitrary SQL to queries via the unsanitized 'val' AJAX parameter. Although the description characterizes attackers as 'unauthenticated,' exploitation in practice requires a Subscriber-level account to obtain a 'get-smart-reply' nonce - a low but real barrier accurately reflected in the CVSS PR:L rating. No public exploit code or CISA KEV listing has been identified at time of analysis, but the trivial nonce-acquisition path (create a ticket, visit the result page) means any user permitted to submit support requests can exploit this on unpatched deployments. Version 1.2.0 appears to resolve the issue based on source code changes in the referenced repository tags.
Technical ContextAI
The vulnerability resides in the smart reply module of the Majestic Support WordPress plugin (CPE: cpe:2.3:a:ahmadmj:majestic_support_-_the_leading-edge_help_desk_&_customer_support_plugin:*:*:*:*:*:*:*:*), specifically in modules/smartreply/model.php (lines 183-184 in both the 1.1.8 and 1.1.9 tags) and the AJAX dispatcher at includes/ajax.php (line 19). The root cause is CWE-89: the 'val' POST parameter is appended directly into an existing SQL query without use of WordPress's $wpdb->prepare() parameterized query interface or adequate escaping, enabling UNION-based or error-based SQL injection. Access to the vulnerable endpoint is gated by a 'get-smart-reply' nonce that WordPress embeds in the ticket detail page (ticketdetail.php line 672), which any user who has filed a ticket can retrieve - making the nonce a soft gate rather than a true privilege barrier. Source code diffs visible in the 1.2.0 tag (modules/smartreply/model.php, revision 3599140, line 212) suggest remediation was applied in that release.
RemediationAI
Upgrade the Majestic Support plugin to version 1.2.0 or later; the 1.2.0 tagged release on plugins.trac.wordpress.org (https://plugins.trac.wordpress.org/browser/majestic-support/tags/1.2.0/modules/smartreply/model.php?rev=3599140#L212) shows revised code in the previously vulnerable model.php location - however, this fix version is inferred from source code diffs rather than from a formal vendor security changelog, so confirm with the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/502577dd-49e3-419d-8b37-591be69ad131 before treating it as definitive. If immediate patching is not possible, disabling public WordPress user registration will prevent external attackers from obtaining the required nonce, though this also blocks legitimate customer self-service ticket creation, which is a significant functional trade-off for a help desk product. A WAF rule blocking SQL metacharacters (single quotes, UNION keywords, comment sequences) in the 'val' POST parameter sent to the plugin's AJAX handler can serve as a compensating control with the trade-off of possible false positives on smart-reply queries containing legitimate apostrophes or SQL-like phrasing. Restricting ticket creation to known, vetted user accounts rather than open registration reduces the attacker population to already-trusted users.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
Same weakness CWE-89 – SQL Injection
View allShare
External POC / Exploit Code
Leaving vuln.today