LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32404: WordPress Studio99 WP Monitor plugin <= 1.0.3 - Broken Access Control vulnerability

Missing Authorization vulnerability in Studio99 Studio99 WP Monitor studio99-wp-monitor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Studio99 WP Monitor: from n/a through <= 1.0.3.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32404 affects the Studio99 WP Monitor WordPress plugin through version 1.0.3. It is a missing authorization issue, meaning unauthenticated users may access functionality or information that should require permission. The reported impact is limited confidentiality exposure, not data modification or service disruption.

Executive priority

Treat as a moderate-priority WordPress exposure. It may allow unauthorized information access, but sources indicate no integrity or availability impact and no confirmed active exploitation. Prioritize internet-facing WordPress sites and environments handling sensitive data.

Technical view

The vulnerability is classified as CWE-862, Missing Authorization, in Studio99 WP Monitor <= 1.0.3. CVSS 3.1 is 5.3: network-accessible, low complexity, no privileges, no user interaction, with low confidentiality impact and no integrity or availability impact. Public sources do not describe specific endpoints, payloads, or a confirmed fixed version.

Likely exposure

Exposure is limited to WordPress sites with the Studio99 WP Monitor plugin installed at version 1.0.3 or earlier. Sites not using this plugin are not affected based on provided sources.

Exploitation context

The CVSS vector indicates unauthenticated network exploitation may be possible. The CVE is not listed as CISA KEV in the provided data, and no cited source confirms active exploitation.

Researcher notes

Public detail is sparse. The record identifies broken access control but does not specify vulnerable routes, required configuration, exploit prerequisites beyond CVSS, or a fixed version. Avoid assuming exploitability details beyond the cited CVSS and CWE data.

Mitigation direction

  • Inventory WordPress sites for Studio99 WP Monitor installations.
  • Identify whether installed versions are 1.0.3 or earlier.
  • Check vendor or Patchstack guidance for a fixed release or workaround.
  • Disable or remove the plugin if not needed.
  • Monitor WordPress access logs for unusual plugin-related requests.

Validation and detection

  • Confirm plugin presence from WordPress administration or asset inventory.
  • Record installed plugin version for each affected site.
  • Compare installed versions against the affected range: through 1.0.3.
  • Review available vendor and Patchstack advisories before making changes.
  • Verify the plugin is updated, disabled, or removed after remediation.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32404 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-32404Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Studio99Studio99 WP Monitorstudio99-wp-monitor, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.