WP Social AutoConnect <= 4.6.2 - Cross-Site Request Forgery to Reflected Cross-Site Scripting
Strategic Overview
- Status
- Patched in 4.6.3
- Affected Plugin
- WP Social AutoConnect
- Affected Version
<= 4.6.2- CVSS
- 6.1Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-12279
At a glance
CVE-2024-12279 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Social AutoConnect WordPress plugin, affecting versions <= 4.6.2. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.6.3; sites on affected versions should update now. Disclosed January 2025, reported by vgo0.
Vulnerability Overview
The WP Social AutoConnect plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.6.2. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in WP Social AutoConnect <= 4.6.2 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WP Social AutoConnect the fix is 4.6.3: builds <= 4.6.2 are affected, anything from 4.6.3 onward is not.
Remediation
Update to version 4.6.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Social AutoConnect: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Social AutoConnect 4.6.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP Social AutoConnect
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C