CVE-2026-18385: Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content <= 4.16.19 - Authenticated (Subscriber+) Arbitrary Shortcode Execution via First Name / Last Name Profile Field
The 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.19. This is due to the software allowing users to execute an action that does not properly validate a value before running doshortcode. This makes it possible for authenticated attackers, with subscriber-level access and above, to execute arbitrary shortcodes. The partial mitigation introduced via stripshortcodes() on [profile-first-name] and [profile-last-name] can be bypassed through the [profile-display-name format="firstlastnames"] render path, the [profile-bio] render path (which re-fetches the raw description meta), and the double-bracket escape sequence [[tag]], all of which allow attacker-controlled shortcode text to reach the outer doshortcode() call.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-18385?
The severity of CVE-2026-18385 is rated medium with a score of 5.4.
How do I fix CVE-2026-18385?
To fix CVE-2026-18385, you should update the Paid Membership Plugin to version 4.16.20 or later.
What kind of attack does CVE-2026-18385 allow?
CVE-2026-18385 allows authenticated users with subscriber or higher roles to execute arbitrary shortcodes.
Which versions of the Paid Membership Plugin are affected by CVE-2026-18385?
CVE-2026-18385 affects all versions of the Paid Membership Plugin up to and including 4.16.19.
What is the impact of CVE-2026-18385 on WordPress sites?
The impact of CVE-2026-18385 includes potential unauthorized execution of shortcodes, which could lead to code injection and security breaches.