ProfilePress CVE-2025-13642
MEDIUMAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister Subscriber-level account
-
DeliveryRequest pp_preview_form endpoint
-
ExploitInject shortcode via type parameter
-
ExecutionServer renders arbitrary shortcode
-
ImpactInformation disclosure or unauthorized action
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access 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 Subscriber-level access or above (PR:L), which is readily obtainable on sites where ProfilePress enables public user registration - the plugin's primary purpose - lowering the practical authentication barrier. The specific prerequisite is reachability of the |
| Impact | This is a genuine-but-moderate priority, not a critical emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N = 5.4 Medium) tells a consistent story: network-reachable, low-complexity, but requiring authentication (PR:L - Subscriber-level account) and yielding only partial confidentiality and integrity impact with no availability impact. The EPSS score of 0.48% (39th percentile) indicates low near-term exploitation probability, and there is no CISA KEV listing and no public exploit identified, so there is no evidence of active or widespread exploitation. The key tension is the 'RCE' tag versus the actual impact: this is arbitrary WordPress SHORTCODE execution, not arbitrary operating-system code execution, and the low C/I and null A impact metrics confirm it is not full RCE - treat the 'RCE' label with skepticism. Because exploitation requires only a Subscriber account (trivially obtainable on sites with open registration, which is ProfilePress's core use case), the authentication barrier is weaker than PR:L normally implies, modestly raising real-world risk on membership/registration sites. Overall: patch promptly on internet-facing sites that allow self-registration, but this is not a drop-everything issue. |
| Exploit ScenarioDerived | An attacker registers a low-privilege Subscriber account on a WordPress site running ProfilePress (self-registration is the plugin's primary feature), then sends a crafted request to the pp_preview_form endpoint supplying a malicious value in the |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Arbitrary shortcode execution in the ProfilePress WordPress plugin (all versions up to and including 4.16.7) lets any authenticated user with Subscriber-level access or above pass an unsanitized type parameter to the pp_preview_form endpoint and have the plugin render attacker-chosen shortcodes in a privileged context. Because ProfilePress is commonly deployed to power public user registration and login forms, the required Subscriber account is frequently self-registerable, which lowers the practical authentication barrier, though real-world impact is bounded by whichever shortcodes exist on the target site and by the assessed low confidentiality and integrity impact with no availability impact. No public exploit code has been identified at time of analysis and the plugin is not listed in CISA KEV; EPSS is low at 0.48% (39th percentile), making this a genuine but moderate-priority issue rather than a critical emergency.
RemediationAI
Update the ProfilePress plugin past version 4.16.7: the upstream fix is available in the WordPress.org changeset at https://plugins.trac.wordpress.org/changeset/3408055/, so an upstream fix is available (PR/commit); the corresponding released patched version is not independently confirmed in the supplied data, so verify the plugin's changelog in the WordPress admin dashboard and update to the first release that includes changeset 3408055, then confirm FormPreviewHandler.php no longer passes the type parameter unsanitized. If immediate update is not possible, compensating controls (each with trade-offs) are: restrict or disable the form preview functionality entirely, which removes a legitimate administrative convenience; disable open/public user registration so unauthenticated visitors cannot self-provision the required Subscriber account, which will block legitimate sign-ups on membership sites that depend on it; and audit or remove Subscriber-level capabilities and sensitive third-party shortcodes on the site, which can break content rendering and plugin functionality. Review site logs for requests to the pp_preview_form endpoint with unusual type values as a post-exploitation indicator, and consult the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/4736d139-814e-4eeb-91e8-5ee41fc35a8f?source=cve for vendor-tracked status.
Affected ProductsAI
The WordPress plugin ProfilePress - distributed under the WordPress.org slug wp-user-avatar and also marketed as the Paid Membership, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content plugin - is affected in all versions up to and including 4.16.7, including the vulnerable FormPreviewHandler code paths referenced in the vendor Trac browser at src/Classes/FormPreviewHandler.php (lines 15 and 71). Any WordPress installation with an active, unpatched copy of this plugin is in scope, regardless of whether paid memberships or ecommerce features are enabled, because the preview endpoint ships with the plugin core. The plugin's own WordPress.org changelog changeset 3408055 documents the fix, and Wordfence threat-intel entry 4736d139-814e-4eeb-91e8-5ee41fc35a8f (linked from NVD) tracks the disclosure.
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 issue is a code-injection flaw (CWE-94) rooted in insufficient sanitization of the type parameter handled by the FormPreviewHandler class in the plugin's form preview functionality (specifically the code paths at FormPreviewHandler.php lines 15 and 71 in the wp-user-avatar plugin slug, which is how ProfilePress is distributed on WordPress.org). WordPress ships a shortcode API in which shortcodes are parsed and executed by do_shortcode(); when a plugin hands user-controlled data to that API without validating the shortcode name or attributes, the attacker can invoke any shortcode registered on the site, not just those the plugin intended. The assessed vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N confirms this is network-reachable, low complexity, requires a low-privileged account (PR:L, i.e. authenticated Subscriber or higher), needs no user interaction, does not change security scope, and yields limited confidentiality and integrity impact with no availability impact. The result is contextual: on a site with plugins or themes exposing sensitive shortcodes (for example those that disclose data or modify content), the same primitive can be chained to greater effect, but the ProfilePress flaw itself is rated moderate.
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:U/C:L/I:L/A:N
Network-reachable endpoint with low complexity and no user interaction, but a Subscriber account is required (PR:L); shortcode execution yields partial confidentiality/integrity with no availability impact.
Primary rating from Vendor (wordfence).
CVSS VectorVendor: wordfence
DescriptionCVE.org
The Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content - ProfilePress plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 4.16.7 due to insufficient input sanitization on the type parameter in the form preview functionality. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary shortcodes via the pp_preview_form endpoint.
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
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
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 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
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB