WP Social AutoConnect
wp-fb-autoconnect · plugin
Known security vulnerabilities for WP Social AutoConnect. Find out in seconds which version runs on your site with WP Lens.
3 known vulnerabilities
2 exploitable without logging in · 1 with no official fix seen · latest Jun 20, 2025
Before you install
Do not install
- 1 record shows no fix in the latest wordpress.org release.
- 1 record needing no login published in the last two years.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 4.6.4 · last updated Aug 13, 2025 · 400+ installs
wordpress.org status checked on Nov 20, 2026
Vulnerabilities
- High 8.8
CVE-2023-37974unauthenticated · needs a click≤ 4.6.1
WordPress WP-FB-AutoConnect Plugin <= 4.6.1 is vulnerable to Cross Site Request Forgery (CSRF)
- Medium 6.1
CVE-2024-12279unauthenticated · needs a click≤ 4.6.2
WP Social AutoConnect <= 4.6.2 - Cross-Site Request Forgery to Reflected Cross-Site Scripting
- Medium 5.9
CVE-2025-50022high privilegeno fix seen
WordPress WP-FB-AutoConnect plugin <= 4.6.4 - Cross Site Scripting (XSS) Vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS). The record lists the latest wordpress.org release (4.6.4) as affected.
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.