Sensitive data extraction via unparameterized lbid query
Published Feb 25, 2025 · Updated Apr 8, 2026
SQL injection in the Yawave plugin for WordPress 2.9.1 and earlier allows remote attackers to extract sensitive database data via lbid. The unauthenticated js_liveblog_update handler places the text-sanitized lbid value into raw SQL in shortcode.liveblog.php and executes it with get_results without parameterization. A public request reaches the handler, enabling blind enumeration of usernames, password hashes, tables, and other data accessible to the WordPress database account.
Summary
What happened
SQL injection in the Yawave plugin for WordPress 2.9.1 and earlier allows remote attackers to extract sensitive database data via lbid. The unauthenticated js_liveblog_update handler places the text-sanitized lbid value into raw SQL in shortcode.liveblog.php and executes it with get_results without parameterization. A public request reaches the handler, enabling blind enumeration of usernames, password hashes, tables, and other data accessible to the WordPress database account.
The record
- CVE
- CVE-2025-1648
- Published
- Feb 25, 2025
- Updated
- Apr 8, 2026
- Vendor
- yawave AG
- Product
- Yawave
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 25, 2025CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.9.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Yawave lbid blind SQL injection requestproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo