Restrict Content CVE-2025-14000
MEDIUMAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain contributor account
-
DeliveryInsert malicious shortcode attribute
-
ExploitStore payload in page
-
ExecutionAdmin views injected page
-
ImpactScript executes in victim browser
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution 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 with contributor-level capability or above on a WordPress site running Restrict Content ≤3.2.15, plus the use of the plugin's 'register_form' or 'restrict' shortcodes where attacker-supplied attributes are rendered. Exploitation is limited by that authentication requirement (not exploitable by anonymous visitors) and by the need for a victim to subsequently load the injected page for the script to fire; it does not depend on a non-default configuration beyond having the vulnerable plugin active and allowing contributor-level content creation. |
| Impact | Moderate, not urgent. The CVSS 3.1 score of 6.4 (vector AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) reflects a stored XSS reachable over the network with low complexity, but it requires PR:L - authenticated contributor-level access or above - which is the single most important mitigating factor and the reason this sits in the medium band rather than critical. Exploitation signals are weak: EPSS is just 0.24% (14th percentile), there is no CISA KEV listing, and no public exploit code was identified, so this is no public exploit identified at time of analysis. The scope-change flag (S:C) correctly captures that injected script executes in the browsers of other users (potentially higher-privileged admins), which is the real escalation risk. All signals are internally consistent - a low-privilege-gated, low-probability stored XSS - so there is no CVSS/EPSS/KEV conflict to flag. Bottom line: a legitimate issue to patch on a normal cycle, but it depends on an attacker first holding a contributor account on the target site, which bounds real-world risk to multi-author/membership sites with untrusted contributors. |
| Exploit ScenarioDerived | A low-trust contributor account on a WordPress site running Restrict Content injects malicious attribute values into a page using the plugin's 'register_form' or 'restrict' shortcode. When an administrator or other user later views that page, the unsanitized script executes in their browser, enabling session/cookie theft or admin-action forgery. No public proof-of-concept exploit is known, and the low attack complexity (AC:L) means exploitation is straightforward once contributor access is obtained. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Stored cross-site scripting (CWE-79) in the WordPress plugin 'Membership Plugin - Restrict Content' through version 3.2.15 lets an authenticated user with contributor-level access or higher inject arbitrary JavaScript that persists in page content and executes for any visitor who later loads the affected page. The flaw lies in the plugin's 'register_form' and 'restrict' shortcodes, which render user-supplied shortcode attributes without adequate sanitization or output escaping; because WordPress grants contributors the ability to create posts, this becomes a realistic privilege-escalation and session-theft vector on sites that permit lower-trust content authoring. Public exploit code has not been identified and there is no confirmed active exploitation (no CISA KEV listing), and EPSS sits at roughly 0.24% (14th percentile), so this is assessed as moderate rather than urgent, though it should still be patched promptly on multi-author sites.
RemediationAI
Vendor-released patch status: upstream fix available (changeset 3420370 in the plugin's trunk, touching core/includes/shortcodes.php and core/includes/member-forms.php); a released patched version number is not independently confirmed in the supplied data, so verify on the plugin's WordPress.org page or the Wordfence advisory whether a version later than 3.2.15 has shipped and upgrade to that version - do not rely on 3.2.15. Until the fixed release is deployed, reduce exposure by tightening who can author content: drop the Contributor role or route all contributor posts through mandatory editorial review, since the injection requires an account at contributor level or above (the trade-off is editorial friction and slower publishing). Administrators can also audit existing posts, pages, and reusable blocks for 'register_form' or 'restrict' shortcodes carrying unexpected attributes and remove any suspicious ones, and enable a WordPress-aware WAF or Content-Security-Policy that blocks inline script execution (CSP may break legitimate plugin or theme inline scripts and requires testing). Sites that do not need front-end membership registration forms can deactivate the plugin entirely, which eliminates the attack surface at the cost of losing content restriction features. Reference advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/0b6a84d7-9e77-4a2f-b065-872e8650e75e and the upstream changeset https://plugins.trac.wordpress.org/changeset/3420370/restrict-content/trunk/core/includes/shortcodes.php.
Affected ProductsAI
All versions of the WordPress plugin 'Membership Plugin - Restrict Content' (plugin slug 'restrict-content') up to and including 3.2.15 running on any WordPress installation where the plugin is active and contributor-level or higher accounts can create content containing the 'register_form' or 'restrict' shortcodes. No CPE identifiers were supplied in the available data, so scoping must be done by plugin slug and version rather than by CPE matching; the vulnerable code paths can be inspected at plugins.trac.wordpress.org/browser/restrict-content/tags/3.2.15/core/includes/shortcodes.php (lines 26 and 135) and plugins.trac.wordpress.org/browser/restrict-content/tags/3.2.15/core/includes/member-forms.php (line 126). The vendor-coordinated advisory is published by Wordfence at wordfence.com/threat-intel/vulnerabilities/id/0b6a84d7-9e77-4a2f-b065-872e8650e75e.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerable component is the WordPress shortcode API as used by the Restrict Content plugin (slug 'restrict-content'). WordPress shortcodes accept positional and named attributes that are parsed and passed to the shortcode callback; the callback is responsible for escaping those values before echoing them into HTML. According to the referenced source, the affected logic lives in core/includes/shortcodes.php (around lines 26 and 135) and core/includes/member-forms.php (around line 126), where attributes supplied to the 'register_form' and 'restrict' shortcodes are placed into the rendered markup without esc_attr()/esc_html() or equivalent context-aware escaping. This is a classic CWE-79 stored/persistent XSS: the payload is saved in post content (which contributors can create), survives in the database, and is served to every subsequent visitor of that page rather than being reflected only to the attacker. The CVSS vector AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N indicates the attacker reaches the site over the network with low privileges, does not need to trick a specific privileged user into a click for the payload to be stored, and that scope is changed - i.e., script executing in a victim's browser within the site's origin can act beyond the vulnerable component itself (e.g., hijacking sessions or performing actions as an administrator who views the page). The referenced changeset 3420370 in the plugin's trunk repository modifies both shortcodes.php and member-forms.php, consistent with adding escaping to shortcode attribute output.
Know when Wordpress Plugin 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:C/C:L/I:L/A:N
Network-reachable stored XSS requiring a contributor account (PR:L), no victim UI to store the payload (UI:N), and S:C because script executes in other users' browser context with low C/I impact.
Primary rating from Vendor (wordfence).
CVSS VectorVendor: wordfence
DescriptionCVE.org
The Membership Plugin - Restrict Content plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'register_form' and 'restrict' shortcodes in all versions up to, and including, 3.2.15 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe 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 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
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB