WordPress MCP Content Manager Lite plugin <= 1.1.0 - Broken Access Control vulnerability

Why this deserves its current priority

CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Jose Conti/mcp-content-manager-lite (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Jose Conti/mcp-content-manager-lite.
2. 2Review the reported fix. Source-reported solution: Update the WordPress MCP Content Manager Lite Plugin to the latest available version (at least 1.2.0).

Evidence timeline and material changes

1. Published upstream

   Sep 30, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 30, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 30, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• WordPress AllAble Connector plugin <= 0.13.4 - Broken Access Control vulnerabilityAlso CWE-862
• WordPress Blocksy Companion plugin <= 2.1.55 - Broken Access Control vulnerabilityAlso CWE-862
• WordPress Prevent files / folders access plugin <= 2.6.7 - Broken Access Control vulnerabilityAlso CWE-862
• WordPress The Events Calendar plugin <= 6.17.5 - Broken Access Control vulnerabilityAlso CWE-862
• WordPress If-So Dynamic Content Personalization plugin <= 1.10.1 - Cross Site Scripting (XSS) vulnerabilitySame generic ecosystem
• WordPress Two Factor plugin <= 0.16.0 - Denial of Service Attack vulnerabilitySame generic ecosystem