Themefic Hydra Booking (hydra-booking) WordPress plugin contains an Improper Neutralization of Special Elements used in an SQL Command (SQL Injection) vulnerability affecting versions through and including 1.1.32. The issue allows SQL injection against the plugin’s database queries due to insufficient sanitization/parameterization of attacker-controlled input.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept (POC) exploit for CVE-2025-68055, an authenticated time-based blind SQL injection vulnerability in the Hydra Booking WordPress plugin (versions <= 1.1.32). The main script, CVE-2025-68055.py, is a Python3 tool that requires valid WordPress credentials to authenticate to the target site. It then exploits the vulnerable /wp-json/hydra-booking/v1/booking/create endpoint by injecting SQL payloads into the 'id' field of a booking creation request. The exploit can enumerate all usernames in the WordPress users table and extract the password hash of a specified user by measuring response times to infer data bit by bit. The repository also includes a README.md with usage instructions and a requirements.txt listing dependencies (requests, argparse). No hardcoded network endpoints are present; all endpoints are relative to the user-supplied target URL. The exploit is a functional POC and does not include weaponized or automated post-exploitation features.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.