Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor-level WordPress credentials
-
DeliveryAccess Content Mask custom post type interface
-
ExploitSubmit publish request without publish capability
-
ExecutionPlugin omits capability check
-
ImpactUnauthorized content published to live site
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
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 | Exploitation requires an authenticated session with at minimum a Contributor role on the target WordPress site. The Content Mask plugin (version 1.8.0-1.8.5.4) must be installed and active. Sites that disable open user registration and restrict Contributor accounts to known, trusted users are not exposed to external attackers. The CVSS vector confirms no user interaction is required once the attacker holds an account, and no special network position is needed. Exploitation is limited in impact to unauthorized content publication - there is no code execution path, no confidentiality impact, and no availability impact. |
| Impact | The vendor-assigned CVSS vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N yields a score of 2.7 (Low). However, the PR:H rating appears inconsistent with the description, which states exploitation requires only a Contributor role - a low-privilege authenticated user in WordPress terms, which maps more accurately to PR:L in CVSS. An independent assessment using PR:L yields approximately 3.7 (Low-Medium), still a low-severity finding. Either way, the real-world risk is constrained: no confidentiality or availability impact exists, scope is unchanged, and the worst outcome is unauthorized content publication rather than code execution or data theft. EPSS at 0.18% (8th percentile) and absence from CISA KEV confirm the security community observes no meaningful exploitation activity. Sites restricting user registration or limiting Contributor accounts to trusted individuals face no practical external threat. |
| Exploit ScenarioDerived | An attacker who holds or registers a Contributor account on a target WordPress site with the Content Mask plugin installed navigates to the plugin's custom post type interface and submits a publish request. Because the plugin omits the capability check, WordPress accepts and publishes the content, bypassing the editorial review queue that Contributors are otherwise subject to. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 23, 2026
Privilege escalation in the Content Mask WordPress plugin (before 1.8.5.5) allows any authenticated Contributor to publish posts and pages without holding the publish capability, bypassing WordPress's role-based access control. The root cause is a missing capability check (CWE-269) when the plugin registers and handles its custom post type publishing workflow. No public exploit identified at time of analysis; EPSS is 0.18% (8th percentile), and the flaw is not listed in CISA KEV, reflecting negligible observed exploitation interest.
RemediationAI
Update the Content Mask WordPress plugin to version 1.8.5.5 or later; vendor patch is confirmed available per the WPScan advisory at https://wpscan.com/vulnerability/1a78993c-1e5c-43fb-9aa4-13edc24100ee/. If immediate patching is not feasible, administrators should audit existing Contributor accounts and remove that role from any untrusted users, since the attack requires an active Contributor-level session. Disabling open user registration eliminates the external attack surface entirely - though this changes site functionality. Note that restricting Contributor access is a compensating control, not a fix; the underlying capability check bypass remains present until the plugin is updated.
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
WordPress enforces content publishing through role-based capability checks - Contributor-level users are explicitly denied the 'publish_posts' capability, limiting them to drafting content for editorial review. The Content Mask plugin creates a custom post type but omits the required current_user_can() gate before allowing publication of that type. CWE-269 (Improper Privilege Management) describes this class of flaw, where a privileged operation is reachable by lower-privileged accounts due to absent or incorrect authorization logic at the plugin layer. The EUVD confirms affected versions span Content Mask 1.8.0 through 1.8.5.4, with the fix introduced in 1.8.5.5.
Know when WordPress 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:H/UI:N/S:U/C:N/I:L/A:N
Contributor is a low-privilege authenticated role (PR:L), not high-privilege; only integrity is affected with no confidentiality or availability impact.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
2DescriptionCVE.org
The Content Mask WordPress plugin before 1.8.5.5 does not check the capability required to publish the post type being created, allowing users with a role as low as Contributor to publish posts and pages on the site without holding the publish capability.
Threat Intelligence Overview
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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
EUVD-2026-64637
GHSA-mfj2-2xr8-6w24
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB