dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-57646

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Subscriber Insecure Direct Object References (IDOR) in Majestic Support <= 1.1.7 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in the Majestic Support plugin affecting versions 1.1.7 and below. The flaw allows authenticated users with Subscriber-level permissions to access or manipulate data objects (such as tickets, records, or files) that should be restricted to higher-privileged users, without proper authorization validation on the server side.

MitigationUpdate Majestic Support to the latest patched version. If no update is available, implement proper object-level authorization checks in the code to verify that the requesting user has permission to access the specific resource before returning data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Majestic Support plugin is installed
    Access the WordPress admin panel and navigate to Plugins > Installed Plugins, or check the wp-content/plugins directory for a folder named 'majestic-support' or similar. Alternatively, query the WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins' AND option_value LIKE '%majestic%';
    Affected if The plugin is present and activated in the WordPress installation
  2. Identify the installed version
    Check the plugin header in the main PHP file (usually wp-content/plugins/majestic-support/majestic-support.php) for the 'Version' comment, or query: SELECT option_value FROM wp_options WHERE option_name = 'majestic_support_version'; Compare the version number to 1.1.7
    Affected if The installed version is 1.1.7 or lower (e.g., 1.1.7, 1.1.6, 1.1.5, etc.)
  3. Verify Subscriber-level user accounts exist
    Check WordPress users with the Subscriber role: In admin, go to Users > All Users and look for users with 'Subscriber' role, or query: SELECT u.user_login, um.meta_value FROM wp_users u LEFT JOIN wp_usermeta um ON u.ID = um.user_id WHERE um.meta_key = 'wp_capabilities' AND um.meta_value LIKE '%subscriber%';
    Affected if At least one user account with Subscriber-level permissions exists in the system
  4. Confirm the vulnerable functionality is accessible
    Test accessing ticket, record, or file endpoints that should require higher privileges (such as viewing other users tickets or accessing admin-level resources). Attempt a request as a Subscriber user to endpoints like /?action=view_ticket&id=1 or similar AJAX/admin-ajax.php routes used by the plugin, without proper authorization headers.
    Affected if Subscriber-level users can access or manipulate data objects (tickets, records, files) belonging to higher-privileged users without receiving a 403/401 authorization error

You are affected if Majestic Support plugin version 1.1.7 or below is installed, Subscriber-level users exist in the system, and those subscribers can access restricted data objects through the plugin's endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Majestic Support to the latest patched version. If no update is available, implement proper object-level authorization checks in the code to verify that the requesting user has permission to access the specific resource before returning data.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57646 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57646 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data