Summary
An arbitrary shortcode execution vulnerability exists in the ProfilePress plugin for WordPress. This affects all versions of the ProfilePress plugin up to and including 4.17.7. A patch is available in version 4.18.0 and later. There is no evidence of active exploitation of this vulnerability.
Affected and patched versions
ProfilePress – Paid Membership, Online Courses (LMS), Ecommerce, User Registration & Login Form, User Profile & Restrict Content (plugin wp-user-avatar): affected 4.17.7 and earlier; fixed in 4.18.0
Is my site vulnerable?
To determine if a WordPress site is exposed to CVE-2026-39733, site administrators must verify the installed version of the ProfilePress – Paid Membership, Online Courses (LMS), Ecommerce, User Registration & Login Form, User Profile & Restrict Content plugin. This vulnerability affects all versions of the plugin up to and including 4.17.7. Sites running version 4.18.0 or later are not affected by this specific issue.
Administrators can check the plugin version through the WordPress administration dashboard. Access the dashboard and navigate to the 'Plugins' section, then select 'Installed Plugins.' On this page, locate the entry for 'ProfilePress – Paid Membership, Online Courses (LMS), Ecommerce, User Registration & Login Form, User Profile & Restrict Content.' The version number is displayed next to the plugin name. If the displayed version is 4.17.7 or any version prior to it, the site is vulnerable. If the version is 4.18.0 or higher, the site has the patch for this vulnerability.
Alternatively, for those with command-line access to their WordPress installation, the WP-CLI tool can provide the plugin version directly. Open a terminal, navigate to the root directory of the WordPress installation, and execute the command: wp plugin get profilepress --field=version. This command will output the currently installed version number of the ProfilePress plugin, allowing for a quick verification against the affected versions. Understanding the installed version is the primary method to assess vulnerability status for this issue.
What an attacker actually does
WordPress shortcodes are special tags that allow users to embed dynamic content or execute specific functions within posts, pages, and other content areas. The ProfilePress – Paid Membership, Online Courses (LMS), Ecommerce, User Registration & Login Form, User Profile & Restrict Content plugin, in versions up to 4.17.7, contains a vulnerability that allows an attacker to execute arbitrary shortcodes. This means an attacker can insert any shortcode they choose into a part of the plugin's functionality that processes user input, even if they are not logged into the website. The attacker does not require any authentication to perform this action.
The root cause of this issue is that the plugin does not properly validate the input it receives before processing it as a shortcode. This lack of validation allows an unauthenticated attacker to bypass security checks and force the website to interpret their malicious input as a legitimate shortcode. Depending on the available shortcodes on a WordPress installation, this can lead to various forms of content injection. For example, an attacker could inject unwanted text, images, or links onto pages managed by ProfilePress, such as membership profiles, course pages, or registration forms. This allows an attacker to alter the visual content presented to site visitors or users.
Beyond simple content injection, this vulnerability also presents a risk of code injection. If a shortcode exists that allows for the execution of script-related HTML tags or other forms of code, an attacker could leverage this to perform Cross-Site Scripting (XSS) attacks. Such attacks might involve injecting malicious JavaScript to steal user session cookies, redirect visitors to malicious websites, or deface parts of the site. The ability to execute arbitrary shortcodes without authentication provides a pathway for attackers to manipulate website content and potentially compromise user data or site integrity through the insertion of unauthorized scripts or content.
How to detect a compromise
Detecting a compromise related to CVE-2026-39733 involves looking for specific indicators that suggest unauthorized shortcode execution or content injection has occurred. Since the vulnerability allows for arbitrary shortcode execution by unauthenticated attackers, the signs of compromise may appear on publicly accessible pages or user-facing elements managed by the ProfilePress plugin.
Begin by performing a visual inspection of pages and forms handled by ProfilePress. This includes membership pages, user profiles, course content, login forms, and registration forms. Look for any unexpected or unauthorized content, such as unusual text, images, links, advertisements, or embedded media that were not intentionally added by site administrators. Pay close attention to areas where shortcodes are typically used or where user-generated content might be displayed.
Review the source code of affected web pages in a browser. Look for unusual script tags (<script>), iframes, or other HTML elements that appear out of place or were not part of the legitimate page design. Malicious scripts injected via shortcodes often manifest in the page's HTML source.
Examine server access logs (e.g., Apache, Nginx logs) for suspicious requests. Look for repeated attempts to access ProfilePress-related URLs with unusual or malformed parameters, especially those containing shortcode-like syntax ([shortcode_name]). Pay attention to requests originating from unfamiliar IP addresses or those that appear to be probing for vulnerabilities. While specific attack patterns may vary, an increase in requests targeting ProfilePress endpoints with unusual POST data could be an indicator.
Inspect the WordPress database for unauthorized content. Shortcodes are often stored within the post_content field of the wp_posts table for pages and posts, or in custom tables used by the ProfilePress plugin for specific features like user profiles or membership settings. Search these tables for unexpected shortcode patterns or content that seems out of context. For example, look for shortcodes that appear to be attempting to embed external content, execute scripts, or create new user accounts. A database query searching for [shortcode within relevant content fields could reveal suspicious entries.
While direct file system changes are less common from shortcode execution alone, if the injected shortcode facilitates further code execution, it could lead to the upload of malicious files, such as web shells. Monitor the WordPress installation for recently modified or newly created files, particularly in directories like wp-content/uploads/, wp-content/plugins/profilepress/, or wp-content/themes/. Regularly compare file checksums against known good versions if a baseline was established.
Finally, review WordPress user accounts for any unauthorized new registrations or modifications to existing user roles and permissions. An attacker exploiting a vulnerability might attempt to create a backdoor user account for persistent access.
How to fix
Update the ProfilePress Plugin: The primary method to address CVE-2026-39733 is to update the ProfilePress – Paid Membership, Online Courses (LMS), Ecommerce, User Registration & Login Form, User Profile & Restrict Content plugin to version 4.18.0 or later. This version contains the necessary patch to resolve the arbitrary shortcode execution vulnerability.
Log in to your WordPress administration dashboard.
Navigate to 'Plugins' -> 'Installed Plugins'.
Locate 'ProfilePress – Paid Membership, Online Courses (LMS), Ecommerce, User Registration & Login Form, User Profile & Restrict Content'.
Click the 'Update Now' link if it is available. If not, ensure your WordPress installation can check for updates or manually update the plugin.
Verify the Update: After updating, confirm that the plugin's version number is 4.18.0 or higher.
Clear Caches: Clear any website caching (plugin-based, server-side, or CDN) to ensure that the updated plugin code is served to all visitors and any potentially cached malicious content is removed.
Check for Compromise: After applying the patch, review your site for any signs of compromise as described in the "How to detect a compromise" section. If any unauthorized content or activity is found, investigate further to remove it and secure your site.
Timeline
Date | Event |
|---|---|
2026-11-07 | Publication |