CVE-2025-13620
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Wp Social Login and Register Social Counter WordPress plugin registers three REST API routes (wslu/v1/check_cache/{type}, wslu/v1/save_cache/{type}, and wslu/v1/settings/clear_counter_cache) with permission_callback set to __return_true, which allows any unauthenticated user to access these endpoints. These handlers also lack capability checks and nonce validation, enabling attackers to clear or overwrite the social counter cache via crafted REST requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the plugin installationCheck if the 'wp-social-login-and-register-social-counter' plugin is present in the WordPress plugins directory (wp-content/plugins/) or via WP-CLI: wp plugin list --name='wp-social'Affected if Plugin is installed and active in WordPress
-
Determine the installed versionCheck the plugin version from the plugin header in wp-content/plugins/wp-social-login-and-register-social-counter/wp-social.php, or via WP-CLI: wp plugin get wp-social-login-and-register-social-counter --format=versionAffected if Version is lower than 3.1.4 (compare your installed version to the affected ranges)
-
Verify REST API endpoint accessibilitySend a GET request to /wp-json/wslu/v1/check_cache/test (no authentication headers) using curl or a browserAffected if Request returns HTTP 200 instead of 401/403, indicating the endpoint is publicly accessible
-
Test cache clearing capabilitySend a POST request to /wp-json/wslu/v1/settings/clear_counter_cache with Content-Type: application/json (no auth headers required)Affected if Request returns HTTP 200 and clears the cache, confirming the vulnerability is exploitable
If the plugin is installed, version is below 3.1.4, and the /wp-json/wslu/ endpoints respond without authentication, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to version 3.1.4 or later which should include proper capability checks and nonce validation on the affected REST endpoints. As a temporary measure, consider blocking unauthenticated access to /wp-json/wslu/ routes via server-level configuration.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13620 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13620 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data