dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-5947

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The Service Finder Bookings plugin for WordPress is vulnerable to privilege escalation via authentication bypass in all versions up to, and including, 6.0. This is due to the plugin not properly validating a user's cookie value prior to logging them in through the service_finder_switch_back() function. This makes it possible for unauthenticated attackers to login as any user including admins.

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 confidence

The Service Finder Bookings WordPress plugin versions up to 6.0 contains an authentication bypass in the service_finder_switch_back() function. The function improperly validates cookie values before using them to log users in, allowing unauthenticated attackers to forge cookie values and authenticate as any existing user on the WordPress site, including administrators.

MitigationUpdate the Service Finder Bookings plugin to version 6.1 or later if available. If no patch exists, disable the plugin immediately and review user accounts for unauthorized administrative access.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Service Finder Bookings' or check the plugin files in wp-content/plugins/ directory for the service-finder-booking folder
    Affected if The plugin is installed and active
  2. Identify installed version
    In WordPress admin, go to Plugins > Installed Plugins, find Service Finder Bookings, and note the version number displayed under the plugin name. Alternatively, check the main plugin file (e.g., service-finder-booking.php) for the 'Version' header in the plugin comments
    Affected if Version is 6.0 or lower (any version up to and including 6.0)
  3. Check if plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify whether Service Finder Bookings shows as 'Active' under the plugin status
    Affected if Plugin is active and version is 6.0 or lower
  4. Verify the vulnerable function exists
    Check plugin source code for the function service_finder_switch_back() - typically found in the main plugin file or includes/classes. Search for 'function service_finder_switch_back' within the plugin directory
    Affected if The function exists in the installed version (present in versions up to 6.0)
  5. Audit user accounts for unauthorized access
    In WordPress admin > Users, review all user accounts with Administrator role. Check for unexpected admin accounts, recently created accounts, or accounts with changed roles. Check user metadata for suspicious last-login timestamps
    Affected if Unexpected administrator accounts exist or suspicious account activity is found

If Service Finder Bookings plugin is active at version 6.0 or lower, the environment is affected by this authentication bypass vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Service Finder Bookings plugin to version 6.1 or later if available. If no patch exists, disable the plugin immediately and review user accounts for unauthorized administrative access.

Recommended fix Moderate confidence

Latest version after 6.0 (contact vendor for specific patched release)

  1. Update the Service Finder Bookings plugin to the latest available version immediately
  2. If immediate update is not possible, disable the plugin temporarily until a patched version is available
  3. Review user accounts for any unauthorized admin accounts created after the vulnerability disclosure
  4. Consider implementing additional authentication mechanisms such as two-factor authentication
  5. Monitor logs for any suspicious login activity using the service_finder_switch_back function

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5947 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5947 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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