CVE-2025-5949
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 is vulnerable to privilege escalation via account takeover in all versions up to, and including, 6.0. This is due to the plugin not properly validating a user's identity prior to processing a password change request. This makes it possible for authenticated attackers with subscriber access or higher to reset other users' passwords, including those of 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 confidenceThe Service Finder Bookings WordPress plugin fails to validate user identity before processing password change requests, allowing any authenticated user with subscriber-level access or higher to reset passwords for other users including administrators, leading to full account takeover and privilege escalation.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Service Finder Bookings plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Service Finder Bookings' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'service-finder-booking' or similar.Affected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn WordPress admin > Plugins, find Service Finder Bookings and read the version number displayed below the plugin name. Alternatively, check the plugin's main PHP file for a 'Version' header comment.Affected if The version number is below 6.1 (e.g., 6.0, 5.9, etc.)
-
Verify user registration is enabledGo to WordPress Settings > General and check if 'Membership - Anyone can register' is enabled, and what default role is set for new users (Subscriber role or higher).Affected if User registration is enabled and allows subscriber-level or higher roles
-
Confirm password reset functionality is accessibleTest accessing the password reset endpoint (typically /wp-login.php?action=lostpassword or the plugin's custom booking endpoint) while logged in as a low-privilege user (subscriber).Affected if A subscriber-level user can access and submit password change requests for other user accounts
A user is affected if the Service Finder Bookings plugin is installed with a version below 6.1 and user registration allows subscriber-level or higher accounts to exist in the system.
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.
dbcve · scopedUpdate to version 6.1 or later when available. Until patched, consider disabling user registration or restricting the plugin, and monitor for unauthorized admin account changes.
Latest version available (newer than 6.0)
- Update the Service Finder Bookings plugin to the latest available version from the WordPress plugin repository or ThemeForest
- After updating, verify that user roles and permissions are functioning correctly
- Ensure all user accounts, especially administrator accounts, have their passwords changed as a precaution since the vulnerability allowed password resets
- Review user accounts for any unauthorized access that may have occurred during the time the vulnerability was exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5949 — 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-5949 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