Loading vulnerability…
CVE-2025-23970 is an incorrect privilege assignment vulnerability in the aonetheme Service Finder Booking plugin. The available information indicates that the flaw allows privilege escalation and affects Service Finder Booking versions through 6.0. Specific vulnerable code paths, functions, and exploitation mechanics are not provided in the supplied content.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
Repository is a small standalone Python exploit project with 3 files: a single executable script (CVE-2025-23970.py), a README, and a license file. The Python script is the clear entry point and implements a web-based exploit workflow against WordPress sites running the Service Finder Bookings plugin. Despite the README describing RCE and a broader exploit framework, the code shown is focused on unauthenticated privilege escalation and user impersonation rather than command execution. Main capabilities in the script include: banner display, target/plugin detection, plugin version extraction via regex, WordPress user enumeration through multiple common endpoints, automated exploitation mode, manual targeting of a specific user ID, SSL verification disabling, and JSON report generation. The exploit logic appears to rely on a missing-authentication issue involving a switch_back parameter and forged cookies, allowing impersonation of arbitrary users, including admins. The script stores cookies in a Requests session and outputs an admin URL for follow-on access. Repository structure is minimal and operational: one Python exploit file with argparse-based CLI, requests for HTTP interactions, regex parsing for version detection, colorama for terminal output, and JSON export support. No evidence indicates use of a larger exploit framework such as Metasploit or Nuclei. Based on the available code, this is a real exploit-oriented PoC/operational script rather than a detector-only tool. However, the README overstates capabilities relative to the visible code, claiming RCE and modular payload support that are not substantiated by the provided script contents.
Repository contains a single Python exploit script (mass-regist.py) plus a short README. The script is a mass-targeting WordPress exploit aimed at the “SF Booking” plugin (README cites CVE-2025-54368). It normalizes target URLs, uses a requests.Session with SSL verification disabled, rotates User-Agent strings, and runs concurrently via ThreadPoolExecutor for scanning/exploitation at scale. Core behavior: for each target, it fetches a page expected to contain a signup/registration nonce, extracts the nonce using multiple regex patterns (get_nonce_signup), then submits a registration payload (generate_user_data) using hardcoded EMAIL/PASSWORD (operator is instructed to edit these). The payload includes role-related fields (e.g., provider-role: package_0) consistent with attempting to abuse a plugin registration workflow to obtain elevated privileges. It also includes a WordPress REST API check to /wp-json/wp/v2/users as a basic fingerprint/validation step. Outputs: writes a run log to registration.log and saves per-target results to success.txt/failed.txt; when successful it also records credentials in credentials.txt. Overall, this is an operational mass exploitation tool (not just detection) focused on creating accounts and attempting admin-level access via a vulnerable WordPress plugin registration mechanism.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.