Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-92536 Overview
The ProfilePress plugin for WordPress contains a sensitive information exposure vulnerability affecting all versions up to and including 4.17.4. The flaw resides in the get_user_profile_structure function and allows authenticated subscribers to harvest other users' email addresses, login names, and registration dates. Attackers abuse per-row user rebinding in the Member Directory by submitting base64-encoded payloads inside the [pp-custom-html] shortcode that invoke [profile-email], [profile-username], and [profile-date-registered] tags. When WordPress's users_can_register option is enabled, unauthenticated attackers can also reach the vulnerable code path through the plugin's registration handler, which processes the reg_nickname and reg_bio fields without a nonce check.
Critical Impact
Mass extraction of WordPress user email addresses and login names enables credential stuffing, targeted phishing, and account takeover against site members.
Affected Products
- ProfilePress (wp-user-avatar) plugin for WordPress — all versions through 4.17.4
- WordPress sites using the Member Directory feature
- WordPress sites with users_can_register enabled (unauthenticated exploitation path)
Discovery Timeline
- 2026-10-03 - CVE-2026-92536 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-92536
Vulnerability Analysis
The vulnerability stems from improper control of generation of code within the ProfilePress shortcode parser [CWE-94]. The plugin's get_user_profile_structure logic reparses shortcodes after resolving a user context inside the Member Directory, rebinding profile tags row by row. An attacker who can inject a [pp-custom-html] shortcode with base64-encoded content causes the parser to decode and expand attacker-chosen profile tags against each listed user. The result is leakage of fields that would otherwise require administrator access to view in bulk.
Root Cause
The Member Directory listing renders user cards by evaluating profile shortcodes against the current row's user ID. The [pp-custom-html] shortcode accepts a base64-encoded body that is decoded and processed through the same shortcode pipeline, including [profile-email], [profile-username], and [profile-date-registered]. Encoding the inner shortcodes bypasses surface-level filters that would otherwise block direct references to private profile tags. The registration handler at RegistrationAuth.php compounds the exposure by accepting reg_nickname and reg_bio inputs without CSRF nonce validation.
Attack Vector
An authenticated subscriber submits attacker-controlled shortcode content through fields that are later rendered inside a Member Directory context. The payload uses [pp-custom-html] with a base64 blob that, once decoded, contains [profile-email] and related tags. When the directory iterates users, each tag resolves against a different account, exfiltrating per-user data. If users_can_register is enabled, the same payload can be delivered through the plugin's registration endpoint by splitting the shortcode across reg_nickname and reg_bio, requiring no authentication and no nonce.
The vulnerability is described in prose because no sanitized proof-of-concept is included in the vendor references. See the Wordfence Threat Intelligence Vulnerability Report and the referenced plugin source files for implementation detail.
Detection Methods for CVE-2026-92536
Indicators of Compromise
- POST requests to the ProfilePress registration endpoint containing reg_nickname or reg_bio values with base64 strings or shortcode fragments such as [pp-custom-html, [profile-email, or [profile-username.
- Unusual spikes in Member Directory page views from a single authenticated subscriber or anonymous IP.
- New subscriber accounts created in rapid succession immediately before Member Directory scraping activity.
- WordPress audit logs showing profile field updates that contain pp-custom-html shortcodes with encoded payloads.
Detection Strategies
- Inspect HTTP request bodies for the literal strings pp-custom-html, profile-email, profile-username, and profile-date-registered paired with base64 patterns.
- Correlate Member Directory render events with downstream requests that iterate pagination parameters, indicating directory scraping.
- Monitor plugin version strings in HTTP responses to identify WordPress sites still running wp-user-avatar at or below 4.17.4.
Monitoring Recommendations
- Enable verbose logging on the WordPress registration endpoint and forward logs to a centralized analytics platform for pattern matching.
- Track user profile update events via a WordPress audit plugin and alert on shortcode content stored in user meta fields.
- Alert on anomalous outbound email volume to addresses that match the format of harvested site member accounts.
How to Mitigate CVE-2026-92536
Immediate Actions Required
- Update the ProfilePress (wp-user-avatar) plugin to a version released after 4.17.4 that addresses this issue.
- Temporarily disable the Member Directory feature if a patched version is not yet available.
- Set the WordPress users_can_register option to disabled unless open registration is a business requirement.
- Rotate credentials for any accounts whose email addresses may have been exposed and enforce multi-factor authentication for all users.
Patch Information
Review the Wordfence Threat Intelligence Vulnerability Report for the fixed version and upgrade guidance. The vulnerable code paths referenced in the advisory include src/Classes/EditUserProfile.php, src/Classes/RegistrationAuth.php, src/ShortcodeParser/FrontendProfileTag.php, and src/Themes/DragDrop/MemberDirectoryListing.php in the wp-user-avatar 4.17.4 source tree.
Workarounds
- Apply a web application firewall rule that blocks POST parameters containing [pp-custom-html] or base64 payloads referencing profile-email, profile-username, or profile-date-registered.
- Restrict access to Member Directory pages so only trusted roles can render the listing.
- Require nonce validation at the reverse proxy layer for the ProfilePress registration endpoint until the plugin is patched.
# Example WAF rule concept for ModSecurity
SecRule ARGS "@rx (?i)(pp-custom-html|profile-email|profile-username|profile-date-registered)" \
"id:1092536,phase:2,deny,status:403,msg:'ProfilePress CVE-2026-92536 shortcode injection attempt'"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

