CVE-2025-2470
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 Service Finder Bookings plugin for WordPress, used by the Service Finder - Directory and Job Board WordPress Theme, is vulnerable to privilege escalation in all versions up to, and including, 5.1. This is due to a lack of restriction on user role in the 'nsl_registration_store_extra_input' function. This makes it possible for unauthenticated attackers to register an account on the site with an arbitrary role, including Administrator, when registering via a social login. The Nextend Social Login plugin must be installed and configured to exploit the vulnerability.
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 Service Finder Bookings WordPress plugin lacks role restriction in the 'nsl_registration_store_extra_input' function, allowing unauthenticated attackers to register with arbitrary roles including Administrator when Nextend Social Login is configured. This privilege escalation occurs during social login registration.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify Service Finder Bookings plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Service Finder Bookings' or check the /wp-content/plugins/ directory for the service-finder-bookings folderAffected if The plugin is installed and active
-
Confirm Nextend Social Login is configuredCheck if Nextend Social Login plugin is active and has at least one social provider configured in WordPress > Social Login > ProvidersAffected if Nextend Social Login is active with at least one provider configured and connected to Service Finder Bookings
-
Compare installed plugin versionView the plugin version on the Plugins page or check the main plugin file header for the Version fieldAffected if The installed version has not received the security patch for CVE-2025-2470
-
Review user accounts for unauthorized administratorsGo to Users > All Users in WordPress admin and inspect the list for admin accounts you did not create, especially those with registration dates matching the timeframe after the plugin was exposedAffected if Unexpected admin-level accounts exist that were not created by legitimate administrators
-
Check user registration logsReview WordPress audit logs, server access logs, or user activity logs for registration events, particularly those using social login providers during the vulnerability windowAffected if Unauthenticated registration events via social login were successful and created accounts with elevated roles
Your environment is affected if Service Finder Bookings is installed with Nextend Social Login configured and unpatched, resulting in unauthorized admin account creation.
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 Service Finder Bookings to the latest patched version. Until patched, disable Nextend Social Login or the vulnerable plugin. Review and remove any unauthorized admin accounts created.
- Consultation3.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2470 — 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-2470 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