WP Social Login and Register Social Counter Plugin REST Endpoint wslu/v1/check_cache/ authorization

Summaryinfo

A vulnerability was found in WP Social Login and Register Social Counter Plugin up to 3.1.3 on WordPress. It has been declared as critical. This affects an unknown function of the file wslu/v1/check_cache/ of the component REST Endpoint. The manipulation results in authorization. This vulnerability is reported as CVE-2025-13620. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability, which was classified as critical, was found in WP Social Login and Register Social Counter Plugin up to 3.1.3 on WordPress. Affected is some unknown processing of the file wslu/v1/check_cache/ of the component REST Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at wordfence.com. This vulnerability is traded as CVE-2025-13620. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 12/06/2025).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• WordPress Plugin

Name

• WP Social Login and Register Social Counter Plugin

Version

• 3.1.0
• 3.1.1
• 3.1.2
• 3.1.3

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion