WP Sticky Social <= 1.0.1 - Cross-Site Request Forgery to Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.0.2
- Affected Plugin
- WP Sticky Social
- Affected Version
1.0.1- CVSS
- 6.1Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-3320
At a glance
CVE-2023-3320 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Sticky Social WordPress plugin, affecting versions 1.0.1. 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 1.0.2; sites on affected versions should update now. Disclosed June 2023, reported by Shunsuke Aoki.
Vulnerability Overview
The WP Sticky Social plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.0.1. This is due to missing nonce validation in the ~/admin/views/admin.php file. This makes it possible for unauthenticated attackers to modify the plugin's settings and 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 Sticky Social 1.0.1 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 Sticky Social the fix is 1.0.2: builds 1.0.1 are affected, anything from 1.0.2 onward is not.
Remediation
Update to version 1.0.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Sticky Social: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Sticky Social 1.0.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C