EUVD-2026-89903
GHSA-xggp-48cx-mp85
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Subscriber account on target site
-
ExploitSend direct request to unprotected plugin endpoint
-
ExecutionMissing capability check permits action
-
ImpactModify or manipulate managed content
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated account at Subscriber level or higher on a WordPress site running MCP Content Manager Lite version 1.1.0 or earlier - per CVSS PR:L, some valid login is mandatory, so this is not exploitable by fully anonymous visitors. Exploitation is most realistic on sites permitting open/self-service user registration, where obtaining a Subscriber account is trivial. No user interaction is required (UI:N) and the attack is fully network-remote (AV:N) with low complexity (AC:L). The limiting factor is the authentication requirement and the plugin's niche deployment; impact is confined to integrity (content manipulation), with no confidentiality disclosure or availability loss per the vector. |
| Impact | This is a moderate-severity broken access control flaw with mixed real-world risk signals. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N, base 6.5) indicates a remotely reachable, low-complexity attack requiring only low-privilege (Subscriber-level) authentication, with a pure integrity impact (I:H) and no confidentiality or availability effect - consistent with CWE-862 Missing Authorization where an under-privileged user can invoke functions or modify content they should not be able to. No EPSS score, no CISA KEV listing, and no public POC are provided, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The primary risk driver is the low authentication barrier (any registered Subscriber, common on sites with open registration) combined with a full integrity impact. Against this, the niche footprint of the plugin and the requirement for an existing account cap real-world exposure. This reads as a genuine-but-not-urgent priority: patch in normal cadence, prioritize higher on sites allowing open user registration. No conflicting signals were detected in the data - the vector and CWE align (BAC with integrity-only impact). |
| Exploit ScenarioDerived | An attacker registers or obtains a low-privilege Subscriber account on a WordPress site running MCP Content Manager Lite <= 1.1.0. They send a direct request to a plugin endpoint (AJAX action or REST route) that lacks a proper capability check, allowing them to create, modify, or delete content they should not control. No public POC is available, but the low complexity and low privilege requirement make exploitation straightforward once the vulnerable endpoint is identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Broken access control in the MCP Content Manager Lite WordPress plugin (versions through 1.1.0) allows an authenticated attacker holding only a Subscriber-level account to modify content that should require higher privileges, with CVSS 6.5 reflecting a high integrity impact but no confidentiality or availability loss. Exploitation is network-remote, low-complexity, and requires no user interaction, but it is gated by the need for a valid low-privileged login (CVSS PR:L), making it most realistic on sites that allow open or self-service user registration; the plugin's niche install base further limits opportunistic abuse. No public exploit code or confirmed active exploitation was identified at time of analysis.
RemediationAI
No vendor-released patch with an exact fixed version is identified in the available data; the Patchstack advisory should be checked directly for an updated release and upgrade applied as soon as a patched version is published. Until then, the most reliable mitigation is to deactivate and remove MCP Content Manager Lite if its functionality is not in active use - side effect: loss of the content-management/MCP integration it provides. If the plugin must remain, close the trivial path to a Subscriber account: disable open/self-service registration (Settings > General) and require invite- or admin-provisioned accounts, since PR:L makes any registered user a potential attacker; trade-off is reduced user onboarding. Additionally, restrict reachability of the plugin's endpoints with a reverse-proxy or WAF rule that blocks requests to the plugin's route from users lacking elevated privileges, or set a virtual patch blocking the specific unauthorized action - side effect: legitimate lower-privileged integrations may break and rules must be tuned per deployment. Finally, audit recent content and post revisions for unauthorized changes and monitor for unexpected modification activity from Subscriber-level sessions, as the impact here is integrity-only.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-862 (Missing Authorization): the plugin performs an action on a content-management operation without verifying that the requesting user holds the capability required for it. In the WordPress capability model this typically means a handler lacks a current_user_can() check (or an equivalent capability/nonce validation), so a Subscriber - the lowest standard role, intended only to read and manage their own profile - can invoke functionality intended for Authors, Editors, or Administrators. The affected component is the MCP Content Manager Lite plugin, published by Jose Conti and tracked by CPE cpe:2.3:a:jose_conti:mcp_content_manager_lite:*:*:*:*:*:*:*:*; the plugin's content-management surface is exposed over HTTP and, as the name implies, is oriented toward programmatic/MCP-style content operations. Notably, the CVSS vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N describes a post-authentication authorization gap rather than an anonymous bypass, even though the source tags include "Authentication Bypass" - the authoritative assessment treats this as a privilege-escalation-style missing-authorization flaw, not a flaw exploitable by unauthenticated visitors. The single available reference (a Patchstack database entry) does not enumerate the specific vulnerable endpoint or parameter, so the exact request path cannot be confirmed from the provided data.
Know when Mcp Content Manager Lite gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Subscriber login gives PR:L; network-remote low-complexity with no interaction; missing authorization yields full integrity impact (I:H) with no confidentiality or availability effect.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Subscriber Broken Access Control in MCP Content Manager Lite <= 1.1.0 versions.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Exploit-DB