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

CVE-2025-6574

HIGH · 8.8 CVSS v3.1 Published 2025-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 account takeover in all versions up to, and excluding, 6.1. This is due to the plugin not properly validating a user's identity prior to updating their details like email. This makes it possible for authenticated attackers, with subscriber-level access and above, to change arbitrary user's email addresses, including administrators, and leverage that to reset the user's password and gain access to their account.

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 fails to validate user identity before allowing email address updates, enabling authenticated attackers with subscriber-level permissions to modify any user's email address including administrators, then reset their password and gain full account access.

MitigationUpdate to version 6.1 or later. If an update is unavailable, consider removing the plugin or implementing additional access controls at the server level to restrict user profile modifications.

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 checks

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

  1. Confirm plugin installation
    Navigate to WordPress admin > Plugins, or check the wp-content/plugins directory for a folder named 'service-finder-bookings' or similar
    Affected if The Service Finder Bookings plugin is present on the site
  2. Identify installed plugin version
    In WordPress admin > Plugins, find Service Finder Bookings and view the version number displayed under the plugin name, or inspect the main plugin PHP file header for 'Version:'
    Affected if The plugin version is installed and is below 6.1 (the fixed version)
  3. Review user accounts for unauthorized email changes
    Go to WordPress admin > Users and compare each user's email address against known-good records or check if any administrator accounts have unfamiliar email addresses
    Affected if Any administrator or high-privilege user account displays an email address that was not set by the legitimate account owner
  4. Audit user profile modification logs
    Check WordPress audit logs, server access logs, or any security logging plugins for POST requests to /wp-admin/admin-ajax.php or user profile update endpoints that originated from subscriber-level accounts modifying other users' profiles
    Affected if Logs show subscriber-level accounts modifying email addresses of administrators or other privileged users

A site is affected if the Service Finder Bookings plugin is installed with a version below 6.1 AND any subscriber-level user account exists on the site, with the definitive sign of exploitation being unauthorized email changes on administrator accounts.

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 to version 6.1 or later. If an update is unavailable, consider removing the plugin or implementing additional access controls at the server level to restrict user profile modifications.

Recommended fix High confidence

6.1

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Service Finder Bookings' plugin in the list
  4. 4. If an update is available, click 'Update Now' to update to version 6.1
  5. 5. Alternatively, download version 6.1 from the official WordPress repository or ThemeForest
  6. 6. Deactivate the existing plugin version
  7. 7. Delete the existing plugin files
  8. 8. Upload and install version 6.1

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6574 — 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-6574 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