CVE-2026-102381: Ahmad Majestic Support broken access control

CVE-2026-102381 · Severity: medium · CVSS 5.3 · Published 2026-10-01

Majestic Support is a WordPress plugin that provides support ticket and customer support functionality. The plugin incorrectly validates user permissions, allowing unauthenticated users to access pages and perform actions they should not be authorized for, such as viewing other users' support tickets or data. An attacker can exploit this to view sensitive customer information without proper authentication.

Technologies: Ahmad Majestic Support. Vendors: Ahmad.

Quick answers

Is CVE-2026-102381 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-102381 being exploited in the wild.
How severe is CVE-2026-102381?
Medium severity, with a CVSS score of 5.3, published 1 October 2026.
Which products and versions are affected?
Ahmad Majestic Support through 1.2.0.
Is there a fix for CVE-2026-102381?
Yes: fixed in 1.2.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-102381 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-102381?
Check whether you run Ahmad Majestic Support at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 1.2.1

Technical details

The plugin fails to properly enforce access control checks, allowing unauthenticated attackers to access restricted pages and perform unauthorized actions. The vulnerability stems from incorrectly configured authorization security levels that do not validate user privileges before granting access to sensitive functionality. No user interaction or authentication is required; the flaw can be exploited directly over the network by an unauthenticated attacker.

Affected products

  • Ahmad Majestic Support through 1.2.0

Timeline

  • 2026-09-21: disclosed: Reported to Patchstack
  • 2026-10-01: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.