Wp Social <= 1.9.0 - Authenticated (Subscriber+) Information Disclosure
Strategic Overview
- Status
- Patched in 2.0
- Affected Plugin
- Wp Social Login and Register Social Counter
- Affected Version
<= 1.9.0- CVSS
- 6.8Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-47160
At a glance
CVE-2022-47160 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Wp Social Login and Register Social Counter WordPress plugin, affecting versions <= 1.9.0. It carries a CVSS score of 6.8 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.0; sites on affected versions should update now. Disclosed December 2022, reported by Dave Jong.
Vulnerability Overview
The Wp Social plugin for WordPress is vulnerable to authorization bypass in versions up to, and including, 1.9.0. This is due to missing capability checks on the 'export_users_content_csv' function. This makes it possible for authenticated attackers with minimal permissions such as subscribers to export user content such as user logins and passwords of various social media providers.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed. A successful exploit has high impact on confidentiality.
CWE-352: Cross-Site Request Forgery (CSRF)
Wp Social Login and Register Social Counter <= 1.9.0 carries this weakness at export_users_content_csv, and reaching it takes an account at Subscriber level or above. 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 Login and Register Social Counter the fix is 2.0: builds <= 1.9.0 are affected, anything from 2.0 onward is not.
Remediation
Update to version 2.0, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Wp Social Login and Register Social Counter 2.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Wp Social Login and Register Social Counter
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C