Social Rocket <= 1.2.9 - Cross-Site Request Forgery

2020-07-22 00:00
Akio Furui

Strategic Overview

Status
Patched in 1.2.10
Affected Version
<= 1.2.9
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all Social Rocket – Social Sharing Plugin vulnerabilities

At a glance

This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Social Rocket WordPress plugin, affecting versions <= 1.2.9. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.2.10; sites on affected versions should update now. Disclosed July 2020, reported by Akio Furui.

Vulnerability Overview

The Social Rocket plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.2.9. This is due to missing or incorrect nonce validation on the admin_settings_post_actions() function. This makes it possible for unauthenticated attackers to gain access to otherwise restricted administrative actions 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Social Rocket <= 1.2.9 carries this weakness at admin_settings_post_actions(), and reaching it 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 Social Rocket the fix is 1.2.10: builds <= 1.2.9 are affected, anything from 1.2.10 onward is not.

Remediation

Update to version 1.2.10, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Social Rocket: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Social Rocket 1.2.10 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C