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-97344 Overview
CVE-2026-97344 is a stored Cross-Site Scripting (XSS) vulnerability in the WP Social Login and Register Social Counter plugin for WordPress. All versions up to and including 3.2.1 are affected. The flaw allows authenticated users with subscriber-level access or above to inject arbitrary web scripts that execute in victim browsers. Exploitation chains two steps: an attacker calls the nonce-only dismiss_ajax_call endpoint to set the xs_social_profile_image user meta flag, then updates their display name to a script payload. The payload renders unescaped through the xs_social_get_avatar function via the avatar alt attribute. The vulnerability is tracked under CWE-79.
Critical Impact
Authenticated subscribers can store JavaScript that executes whenever any user — including administrators — views pages rendering the attacker's avatar, enabling session theft and privilege escalation paths.
Affected Products
- WP Social Login and Register Social Counter plugin for WordPress — all versions ≤ 3.2.1
- WordPress sites with subscriber registration enabled using the affected plugin
- Any WordPress deployment where the plugin renders user avatars via xs_social_get_avatar
Discovery Timeline
- 2026-10-03 - CVE-2026-97344 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-97344
Vulnerability Analysis
The vulnerability resides in the plugin's avatar rendering logic at app/avatar.php. When a user has the xs_social_profile_image meta flag set, the plugin takes an alternate output branch that emits an <img> tag incorporating the user's display name as the alt attribute. The display name passes through WordPress core sanitization using the ENT_NOQUOTES flag, which preserves single and double quotes in the output string. This preservation allows an attacker to break out of the alt attribute and inject arbitrary HTML and script content. The injected markup persists in page output wherever the plugin renders the attacker's avatar, including author archives, comment threads, and administrative user listings.
Root Cause
The root cause combines insufficient output escaping with a missing authorization check on the meta-writing endpoint. The dismiss_ajax_call AJAX handler validates only a nonce, and that nonce is accessible to any authenticated user — including subscribers — from any wp-admin page. The handler permits writing arbitrary user meta keys, enabling an attacker to toggle xs_social_profile_image on their own account. The xs_social_get_avatar function then selects the vulnerable rendering branch and emits the display name without context-appropriate escaping for an HTML attribute.
Attack Vector
Exploitation requires a subscriber-level account and proceeds in two stages. First, the attacker loads any wp-admin page to obtain the AJAX nonce, then issues a request to the dismiss_ajax_call endpoint to set xs_social_profile_image on their own user ID. Second, the attacker updates their WordPress display name to a payload such as an alt-attribute breakout containing an inline event handler. When administrators or other users view any page that renders the attacker's avatar through the plugin, the injected script executes in the victim's browser session.
The vulnerability mechanism is documented in the affected source at WordPress Avatar File Code and the Wordfence Vulnerability Report.
Detection Methods for CVE-2026-97344
Indicators of Compromise
- User meta entries where xs_social_profile_image is set for low-privilege accounts, especially subscribers who did not legitimately upload a social profile image.
- User display names in the wp_users table containing HTML characters such as ", ', <, >, or onerror= / onload= substrings.
- Unexpected outbound requests from administrator browsers to attacker-controlled domains shortly after viewing user listings or author archive pages.
Detection Strategies
- Query the wp_usermeta table for the xs_social_profile_image key and correlate against expected social-login users to identify anomalous assignments.
- Inspect page responses rendering user avatars for <img> tags whose alt attribute contains quote characters or HTML tags.
- Review web server access logs for POST requests to admin-ajax.php with action=dismiss_ajax_call originating from subscriber accounts.
Monitoring Recommendations
- Alert on any modification to the display_name column in wp_users for accounts other than administrators and editors.
- Monitor for repeated subscriber-origin calls to admin-ajax.php endpoints that write user meta.
- Deploy Content Security Policy (CSP) reporting to capture inline-script execution violations originating from WordPress pages.
How to Mitigate CVE-2026-97344
Immediate Actions Required
- Update the WP Social Login and Register Social Counter plugin to a version later than 3.2.1 as soon as the vendor releases a patched build.
- Audit existing user accounts for suspicious display_name values and clear any entries containing HTML or script syntax.
- Remove the xs_social_profile_image user meta entry from any account that was not expected to carry a social profile image.
Patch Information
The vendor has committed a fix referenced in the WordPress Social Changeset. Site operators should apply the updated plugin release that includes this changeset. Additional context is available in the Wordfence Vulnerability Report.
Workarounds
- Deactivate the WP Social Login and Register Social Counter plugin until a patched version is installed.
- Restrict new user registration or require administrator approval for subscriber accounts to limit the attacker population.
- Deploy a web application firewall rule to block POST requests to admin-ajax.php with action=dismiss_ajax_call from non-privileged roles.
- Enforce a strict Content Security Policy that disallows inline event handlers to reduce the impact of attribute-breakout XSS.
# Example WP-CLI commands to audit and remediate affected accounts
wp user meta list --format=csv | grep xs_social_profile_image
wp user meta delete <user_id> xs_social_profile_image
wp user list --role=subscriber --fields=ID,user_login,display_name
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

