# CVE-2025-13620: Missing authorization in Wp Social Login and Register Social Counter

> Unauthenticated attackers can tamper with social counter caches via REST endpoints due to missing authorization checks in the WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-pgg4-37vc-q6h2

## What is CVE-2025-13620?

CVE-2025-13620 is a medium-severity missing authorization vulnerability in roxnor Wp Social Login and Register Social Counter, published on 5 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-13620?


## How do I fix CVE-2025-13620?

No fix has been published for CVE-2025-13620 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-13620 being exploited?

There is no known exploitation of CVE-2025-13620 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13620 and fix it if it is affected.

What it is: CVE-2025-13620 is a medium-severity missing authorization vulnerability in roxnor Wp Social Login and Register Social Counter, published on 5 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13620 in the wild and no public exploit code.

Affected product: roxnor Wp Social Login and Register Social Counter. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-13620/ (Markdown: https://insights.sbomify.com/CVE-2025-13620/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-13620
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-13620
- OSV: https://osv.dev/vulnerability/CVE-2025-13620

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-13620/
Summaries are generated and may contain mistakes; the official description above is the record.