Mcp Server For Wordpress
Monthly
Cross-site request forgery in the MCP Server for WordPress plugin (all versions before 1.8.2) allows unauthenticated attackers to perform administrator-only actions - including creating a brand-new administrator account - by tricking a logged-in WordPress administrator into visiting a crafted page. The plugin fails to correctly verify the WordPress REST API nonce for cookie-authenticated requests when an attacker-influenceable condition is present, so the victim's admin session is abused without any credential from the attacker (CVSS 3.1: 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-352). Publicly available exploit code exists per WPScan, but there is no confirmation of active exploitation (not in CISA KEV; SSVC exploitation: none) and EPSS is a low 0.10% (1st percentile); the practical gate is that a logged-in administrator must be lured to an attacker-controlled page while the vulnerable plugin is active.
Contributor-level users on WordPress sites running the MCP Server for WordPress plugin before 1.8.2 can enumerate the title and publication status of any post, page, or custom post type - including other users' private, draft, pending, and scheduled content - by calling a workflow REST route that performs no object-level authorization check. The impact is read-only metadata disclosure (CWE-200): no post bodies, no write access, and no availability impact, and EPSS is 0.14% (3rd percentile) with no KEV listing, though publicly available exploit code exists. Exploitation requires an authenticated account with at least the Contributor role on an affected site, and one metric disagreement is worth flagging: the published CVSS vector rates PR:H (score 2.7) while our independent assessment rates PR:L, matching the publicly documented Contributor-level access path and raising the assessed base score accordingly.
The MCP Server for WordPress plugin before 1.8.2 exposes workflow create, update, and delete REST routes that fail to enforce ownership or sufficient capability checks, allowing an authenticated Contributor-level user to create, modify, or delete site-wide workflow configuration, including workflows originally created by administrators. Attackers need valid low-privilege WordPress credentials but no user interaction and no special configuration beyond an active plugin, making this an integrity-only authorization bypass with no confidentiality or availability impact; publicly available exploit code exists and proof-of-concept details are referenced in the WPScan advisory. EPSS is very low at 0.13% (2nd percentile), CISA SSVC reports no known exploitation, and the vendor has released a fix in 1.8.2.
Cross-site request forgery in the MCP Server for WordPress plugin (all versions before 1.8.2) allows unauthenticated attackers to perform administrator-only actions - including creating a brand-new administrator account - by tricking a logged-in WordPress administrator into visiting a crafted page. The plugin fails to correctly verify the WordPress REST API nonce for cookie-authenticated requests when an attacker-influenceable condition is present, so the victim's admin session is abused without any credential from the attacker (CVSS 3.1: 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-352). Publicly available exploit code exists per WPScan, but there is no confirmation of active exploitation (not in CISA KEV; SSVC exploitation: none) and EPSS is a low 0.10% (1st percentile); the practical gate is that a logged-in administrator must be lured to an attacker-controlled page while the vulnerable plugin is active.
Contributor-level users on WordPress sites running the MCP Server for WordPress plugin before 1.8.2 can enumerate the title and publication status of any post, page, or custom post type - including other users' private, draft, pending, and scheduled content - by calling a workflow REST route that performs no object-level authorization check. The impact is read-only metadata disclosure (CWE-200): no post bodies, no write access, and no availability impact, and EPSS is 0.14% (3rd percentile) with no KEV listing, though publicly available exploit code exists. Exploitation requires an authenticated account with at least the Contributor role on an affected site, and one metric disagreement is worth flagging: the published CVSS vector rates PR:H (score 2.7) while our independent assessment rates PR:L, matching the publicly documented Contributor-level access path and raising the assessed base score accordingly.
The MCP Server for WordPress plugin before 1.8.2 exposes workflow create, update, and delete REST routes that fail to enforce ownership or sufficient capability checks, allowing an authenticated Contributor-level user to create, modify, or delete site-wide workflow configuration, including workflows originally created by administrators. Attackers need valid low-privilege WordPress credentials but no user interaction and no special configuration beyond an active plugin, making this an integrity-only authorization bypass with no confidentiality or availability impact; publicly available exploit code exists and proof-of-concept details are referenced in the WPScan advisory. EPSS is very low at 0.13% (2nd percentile), CISA SSVC reports no known exploitation, and the vendor has released a fix in 1.8.2.