CVE-2026-102381: WordPress Majestic Support plugin <= 1.2.0 - Broken Access Control vulnerability

Q: Who can exploit this issue?

The vulnerability is network-accessible and requires no privileges or user interaction, so an unauthenticated remote attacker may be able to exploit it.

Q: What versions are affected?

Majestic Support versions through 1.2.0 are affected. No fixed version is identified in the provided information.

Q: What is the potential impact?

The reported impact is limited to integrity, meaning an attacker may be able to make unauthorized modifications. No confidentiality or availability impact is identified.

Q: What should teams do if they cannot patch immediately?

The provided information does not identify a workaround or mitigation. Restricting unnecessary public access to the affected WordPress installation may reduce exposure, but no product-specific compensating control is provided.

Published Oct 1, 2026

Updated

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.

Affected Software

1 affected component

Ahmad Majestic Support<=1.2.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade WordPress Majestic Support plugin to a version that resolves this vulnerability.
Fixed in 1.2.1

Event History

Oct 1, 2026

CVE Published

via MITRE·12:28 PM

Data Sourced

via MITRE·12:28 PM

RemedyDescriptionSeverityWeakness

Frequently Asked Questions

Who can exploit this issue?

The vulnerability is network-accessible and requires no privileges or user interaction, so an unauthenticated remote attacker may be able to exploit it.

What versions are affected?

Majestic Support versions through 1.2.0 are affected. No fixed version is identified in the provided information.

What is the potential impact?

The reported impact is limited to integrity, meaning an attacker may be able to make unauthorized modifications. No confidentiality or availability impact is identified.

What should teams do if they cannot patch immediately?

The provided information does not identify a workaround or mitigation. Restricting unnecessary public access to the affected WordPress installation may reduce exposure, but no product-specific compensating control is provided.

CVE-2026-102381: WordPress Majestic Support plugin <= 1.2.0 - Broken Access Control vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

Who can exploit this issue?

What versions are affected?

What is the potential impact?

What should teams do if they cannot patch immediately?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

What versions are affected?

What is the potential impact?

What should teams do if they cannot patch immediately?