CVE-2026-57646

Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin <= 1.1.7 - Authenticated (Subscriber+) Insecure Direct Object Reference

2026-06-26 00:00
William Matos

Strategic Overview

Status
Patched in 1.1.8
Affected Plugin
Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin
Affected Version
<= 1.1.7
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-57646
View all Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin vulnerabilities

At a glance

CVE-2026-57646 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Majestic Support WordPress plugin, affecting versions <= 1.1.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.1.8; sites on affected versions should update now. Disclosed June 2026, reported by William Matos.

Vulnerability Overview

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.1.7 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform unauthorized actions.

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 interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Majestic Support <= 1.1.7 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Majestic Support the fix is 1.1.8: builds <= 1.1.7 are affected, anything from 1.1.8 onward is not.

Remediation

Update to version 1.1.8, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Majestic Support 1.1.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-57646https://www.wordfence.com/threat-intel/vulnerabilities/id/e8e2dbf9-f6b5-4328-92c5-5d46a4097235https://nvd.nist.gov/vuln/detail/CVE-2026-57646

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C