Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalPublic exploit

Authentication Bypass in Service Finder Bookings WordPress Plugin

IdentifiersCVE-2025-5947CWE-287

CVE-2025-5947 is a critical authentication bypass / privilege escalation vulnerability in the Service Finder Bookings plugin bundled with the Service Finder WordPress theme. It affects all versions up to and including 6.0. The flaw is caused by improper validation of a user-controlled cookie value before authenticating a session in the account-switching routine service_finder_switch_back(). Specifically, the plugin trusts cookie data associated with the original_user_id account-switching mechanism without sufficiently verifying that the requester is legitimately authorized to switch back into that account. As a result, an unauthenticated attacker can forge the relevant cookie and invoke the switch_back flow to log in as any WordPress user, including an administrator.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows unauthenticated takeover of arbitrary WordPress accounts, including administrator accounts. With admin access, an attacker can fully compromise the site: modify content and settings, upload PHP files, inject malicious code, create redirects to phishing or malware sites, export database contents, establish persistence, and potentially erase traces of compromise. Public reporting indicates the vulnerability has been actively exploited in the wild.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, temporarily disable the vulnerable Service Finder Bookings functionality or the affected theme/plugin component, and restrict administrative and login-related access to trusted IPs where operationally feasible. Monitor logs for requests involving the switch_back parameter and suspicious use of the original_user_id cookie, and consider blocking known attacking IPs observed in exploitation reporting. Web application firewall protections, including Wordfence rules that detect the malicious cookie pattern, may reduce exposure but should not be treated as a substitute for upgrading.

Remediation

Patch, then assume compromise.

Upgrade the Service Finder theme / bundled Bookings plugin to version 6.1 or later, which reportedly fixes the issue and was released on July 17, 2025. After patching, review WordPress users, administrator accounts, plugin/theme files, uploaded PHP files, site content, redirects, scheduled tasks, and logs for signs of unauthorized access or persistence. Rotate administrator credentials and invalidate active sessions if compromise is suspected.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app
CVE-2025-5947MaturityPoCVerified exploit

Repository contains a standalone Python exploit for CVE-2025-5947 affecting the WordPress Service Finder Bookings (sf-booking) plugin. Structure is minimal: one executable Python script, one README with usage and vulnerability background, and a requirements file listing requests/urllib3 dependencies. The main script defines a CVE20255947Exploit class with three core capabilities: (1) target validation by probing /wp-admin/ and /wp-content/plugins/sf-booking/, (2) exploitation by sending a GET request to /wp-admin/admin-ajax.php with action=service_finder_switch_back and a forged original_user_id cookie, and (3) brute-force enumeration of multiple numeric user IDs to identify accounts that can be impersonated. Success is inferred from HTTP 301/302 redirects, a Location header containing /wp-admin/, and a Set-Cookie header containing wordpress_logged_in_. The exploit is a real offensive tool rather than a detector: it actively attempts to obtain an authenticated WordPress session as an arbitrary user, typically admin ID 1. No advanced post-exploitation payload is included; the script focuses solely on authentication bypass via cookie spoofing.

xxconiDisclosed May 30, 2026pythonmarkdownwebnetwork
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity35

Community discussion across Reddit, Mastodon, and other social sources.