HomeWordPress vulnerabilitiesMajestic Support
Majestic Support vulnerabilities
Majestic Support has 8 known vulnerabilities in this database. The most recent published record is dated 18 Nov 2026.
- Known vulnerabilities
- 8
- Active installs
- 3,000+
- Latest version
- 1.2.4
- Last updated
- 1 Nov 2026
- Most recent
- 18 Nov 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-126699 | Medium 6.1 | Up to 1.2.4 | No fixed version yet | 4 d ago |
| SQL injection CVE-2026-115820 | Medium 6.5 | Up to 1.2.2 | Fixed in a later version (latest 1.2.4) | 30 Oct 2026 |
| Broken access control CVE-2026-112218 | Medium 5.3 | Up to 1.2.1 | Fixed in a later version (latest 1.2.4) | 22 Oct 2026 |
| Broken access control CVE-2026-102382 | Medium 4.3 | Up to 1.2.0 | Fixed in a later version (latest 1.2.4) | 1 Oct 2026 |
| Broken access control CVE-2026-102381 | Medium 5.3 | Up to 1.2.0 | Fixed in a later version (latest 1.2.4) | 1 Oct 2026 |
| SQL injection CVE-2026-13262 | Medium 6.5 | Up to 1.1.9 | Fixed in a later version (latest 1.2.4) | 11 Jul 2026 |
| Sensitive data exposure CVE-2024-13600 | High 7.5 | Before 1.0.6 | Fixed in 1.0.6 | 12 Feb 2025 |
| Broken access control CVE-2024-13601 | Medium 4.3 | Before 1.0.6 | Fixed in 1.0.6 | 12 Feb 2025 |
Read the published descriptions
- CVE-2026-126699, 18 Nov 2026
- The Majestic Support - The Leading-Edge Help Desk & Customer Support Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'mjsupport_message' parameter in all versions up to, and including, 1.2.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires that a staff member or administrator opens the affected ticket and clicks the attacker-planted link on the ticket-detail screen, as the VenoBox payload is triggered on click rather than on page load. Successful exploitation additionally requires an action by an administrator - the attacker cannot trigger the vulnerability on their own. CVE record
- CVE-2026-115820, 30 Oct 2026
- The Majestic Support - The Leading-Edge Help Desk & Customer Support Plugin plugin for WordPress is vulnerable to generic SQL Injection via the 'columns (array keys)' parameter in all versions up to, and including, 1.2.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Any authenticated WordPress user with Subscriber-level access can exploit this because the 'saveusereraserequest' task is whitelisted for front-end customer use, the plugin auto-provisions a help-desk record for every WordPress account, and the only guard is a nonce the attacker legitimately obtains from their own 'Add erase request' page. CVE record
- CVE-2026-112218, 22 Oct 2026
- Missing Authorization vulnerability in Ahmad Majestic Support majestic-support allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Majestic Support: from n/a through 1.2.1. CVE record
- CVE-2026-102382, 1 Oct 2026
- Authorization Bypass Through User-Controlled Key vulnerability in Ahmad Majestic Support majestic-support allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Majestic Support: from n/a through 1.2.0. CVE record
- CVE-2026-102381, 1 Oct 2026
- Missing Authorization vulnerability in Ahmad Majestic Support majestic-support allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Majestic Support: from n/a through 1.2.0. CVE record
- CVE-2026-13262, 11 Jul 2026
- 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. CVE record
- CVE-2024-13600, 12 Feb 2025
- The Majestic Support - The Leading-Edge Help Desk & Customer Support Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.0.5 via the 'majesticsupportdata' directory. This makes it possible for unauthenticated attackers to extract sensitive data stored insecurely in the /wp-content/uploads/majesticsupportdata directory which can contain file attachments included in support tickets. CVE record
- CVE-2024-13601, 12 Feb 2025
- The Majestic Support - The Leading-Edge Help Desk & Customer Support Plugin plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.0.5 via the 'exportusereraserequest' function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to export ticket data for any user. CVE record
What to do if you run Majestic Support
If you run Majestic Support, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Majestic Support vulnerabilities
Free. We email you when a new vulnerability is published for Majestic Support, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.