Social Rocket – Social Sharing Plugin <= 1.3.4 - Missing Authorization to Settings Update
Strategic Overview
- Status
- Patched in 1.3.4.1
- Affected Plugin
- Social Rocket – Social Sharing Plugin
- Affected Version
<= 1.3.4- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-9697
At a glance
CVE-2024-9697 is a medium-severity Missing Authorization vulnerability in the Social Rocket WordPress plugin, affecting versions <= 1.3.4. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.3.4.1; sites on affected versions should update now. Disclosed January 2025, reported by Tieu Pham Trong Nhan.
Vulnerability Overview
The Social Rocket – Social Sharing Plugin plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the tweet_settings_save() and tweet_settings_update() functions in all versions up to, and including, 1.3.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update the plugin's settings.
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, and no interaction from a victim user.
CWE-862: Missing Authorization
Social Rocket <= 1.3.4 carries this weakness at tweet_settings_save(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Social Rocket the fix is 1.3.4.1: builds <= 1.3.4 are affected, anything from 1.3.4.1 onward is not.
Remediation
Update to version 1.3.4.1, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Social Rocket 1.3.4.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Social Rocket – Social Sharing Plugin
- 8.8Social Rocket <= 1.2.9 Cross-Site Request Forgery
- 8.8CVE-2020-5611: Social Rocket – Social Sharing Plugin < 1.2.10 CSRF
CVE-2020-5611 - 6.4CVE-2026-1923: Social Rocket – Social Sharing Plugin Stored XSS
CVE-2026-1923 - 6.4CVE-2024-9702: Social Rocket <= 1.3.4 Stored Cross-Site Scripting
CVE-2024-9702 - 6.1CVE-2024-37258: Social Rocket <= 1.3.3 Reflected Cross-Site Scripting
CVE-2024-37258 - 5.5CVE-2022-3136: Social Rocket <= 1.3.2 Stored Cross-Site Scripting
CVE-2022-3136
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C