Wp Social Login and Register Social Counter <= 3.1.3 - Missing Authorization in Cache REST Endpoints to Social Counter Tampering
Strategic Overview
- Status
- Patched in 3.1.4
- Affected Plugin
- Wp Social Login and Register Social Counter
- Affected Version
<= 3.1.3- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-13620
At a glance
CVE-2025-13620 is a medium-severity Missing Authorization vulnerability in the Wp Social Login and Register Social Counter WordPress plugin, affecting versions <= 3.1.3. 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 3.1.4; sites on affected versions should update now. Disclosed December 2025, reported by Dmitrii Ignatyev.
Vulnerability Overview
The Wp Social Login and Register Social Counter plugin for WordPress is vulnerable to missing authorization in versions up to, and including, 3.1.3. This is due to the REST routes wslu/v1/check_cache/{type}, wslu/v1/save_cache/{type}, and wslu/v1/settings/clear_counter_cache being registered with permission_callback set to __return_true and lacking capability or nonce validation in their handlers. This makes it possible for unauthenticated attackers to clear or overwrite the social counter cache via crafted REST requests.
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
Reaching this weakness in Wp Social Login and Register Social Counter <= 3.1.3 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 Wp Social Login and Register Social Counter the fix is 3.1.4: builds <= 3.1.3 are affected, anything from 3.1.4 onward is not.
Remediation
Update to version 3.1.4, 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: Wp Social Login and Register Social Counter 3.1.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Wp Social Login and Register Social Counter
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C