Skip to main content
Vulnerability Database/CVE-2025-50022

CVE-2025-50022: WP-FB-AutoConnect Stored XSS Vulnerability

CVE-2025-50022 is a stored cross-site scripting vulnerability in the WP-FB-AutoConnect WordPress plugin that enables attackers to inject malicious scripts. This article covers technical details, affected versions, and mitigation.

Published:

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-2025-50022 Overview

CVE-2025-50022 is a stored Cross-Site Scripting (XSS) vulnerability in the JK WP-FB-AutoConnect WordPress plugin [CWE-79]. The flaw affects all plugin versions up to and including 4.6.4. An authenticated attacker with high privileges can inject malicious scripts that persist on the site and execute in the browsers of visiting users. The injected payload executes in the context of the victim's session, enabling session theft, content manipulation, or redirection to attacker-controlled infrastructure.

Critical Impact

Successful exploitation allows persistent script injection that executes against site administrators and visitors, with a scope change that extends impact beyond the vulnerable component.

Affected Products

  • JK WP-FB-AutoConnect WordPress plugin versions up to and including 4.6.4
  • WordPress sites running the WP-FB-AutoConnect plugin for Facebook authentication
  • All deployments where the plugin remains active on the WordPress installation

Discovery Timeline

  • 2025-06-20 - CVE CVE-2025-50022 published to NVD
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2025-50022

Vulnerability Analysis

The vulnerability stems from improper neutralization of user-supplied input during web page generation. Input accepted by the WP-FB-AutoConnect plugin is reflected into rendered HTML output without adequate sanitization or output encoding. An attacker with authenticated access can store a crafted payload that persists in the WordPress database. The payload later executes in the browser of any user who loads the affected page.

Because the vulnerability has a changed scope, injected scripts can affect resources outside the plugin's own security context. The payload runs with the privileges of the viewing user, which commonly includes administrators managing plugin configuration. Attackers can leverage this to steal authentication cookies, perform actions on behalf of the user, or pivot to further attacks against the WordPress environment.

Root Cause

The root cause is the absence of proper input sanitization and output encoding in plugin functions that render user-controlled data. WordPress exposes sanitization helpers such as sanitize_text_field() and output encoders such as esc_html() and esc_attr(). The plugin fails to apply these consistently when storing or rendering administrator-controlled values up to version 4.6.4.

Attack Vector

Exploitation requires network access to the WordPress site and authenticated access with elevated privileges. The attacker submits a crafted payload through a plugin input field. User interaction is required when a victim loads the page that renders the stored payload. The vulnerability mechanism and affected parameters are documented in the Patchstack XSS Vulnerability Report.

Detection Methods for CVE-2025-50022

Indicators of Compromise

  • Unexpected <script> tags, event handlers, or encoded JavaScript present in WordPress database tables tied to the WP-FB-AutoConnect plugin configuration
  • Outbound requests from administrator browsers to unknown domains shortly after loading plugin pages
  • New or modified WordPress administrator accounts created without a corresponding legitimate workflow

Detection Strategies

  • Audit the wp_options and plugin-specific tables for stored values containing HTML or JavaScript syntax
  • Review web server access logs for POST requests to plugin administrative endpoints containing encoded script payloads
  • Deploy a web application firewall rule set that flags XSS payload patterns targeting WordPress admin paths

Monitoring Recommendations

  • Enable WordPress audit logging to capture changes to plugin settings and administrator activity
  • Monitor administrator session behavior for anomalous API calls or unexpected content modifications
  • Alert on installations of WP-FB-AutoConnect at or below version 4.6.4 across managed WordPress estates

How to Mitigate CVE-2025-50022

Immediate Actions Required

  • Deactivate the WP-FB-AutoConnect plugin on all WordPress sites running version 4.6.4 or earlier until a vendor patch is confirmed
  • Rotate credentials and invalidate active sessions for all WordPress administrators who accessed plugin pages
  • Review the WordPress database for persisted payloads and remove any malicious entries

Patch Information

At the time of publication, no fixed version has been identified in the available advisory data. Monitor the Patchstack XSS Vulnerability Report for updates on a vendor-supplied fix. If no patched release becomes available, consider removing the plugin and replacing it with a maintained alternative.

Workarounds

  • Restrict access to the WordPress administrative interface using IP allowlists or VPN-only access
  • Enforce a Content Security Policy that disallows inline scripts to limit the impact of injected payloads
  • Apply web application firewall rules that block XSS payload patterns targeting the plugin's input parameters
bash
# Example WordPress CLI command to disable the vulnerable plugin
wp plugin deactivate wp-fb-autoconnect
wp plugin delete wp-fb-autoconnect

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.