A serious wpForo vulnerability can let unauthenticated attackers extract usernames, password hashes and session data from WordPress sites. GajIPS detects the attack.
Severity: HIGH · Priority: P2 — active exploitation of an unauthenticated WordPress forum SQLi, investigate on hit
These rules detect exploitation attempts against CVE-2026-1581, an unauthenticated SQL injection vulnerability in the wpForo Forum plugin for WordPress, confirmed under active exploitation as of October 2026. The plugin affects WordPress installations running wpForo Forum version 2.4.14 or earlier. The flaw sits in a forum sort-order parameter (wpfob) that the plugin passes directly into an SQL ORDER BY clause after only basic text sanitisation, without parameterised query preparation. Because the parameter is read before authentication is checked, an unauthenticated visitor can inject arbitrary SQL expressions — in practice, time-delay functions that allow an attacker to determine the truth value of any database condition one bit at a time, and by extension to extract the entire contents of the WordPress database including usernames, password hashes, and session tokens. The primary rule watches for the injection in the GET query string, where the plugin reads it in all confirmed exploits; the second rule provides additional coverage for the POST body.
A hit indicates an active database extraction attempt against a WordPress site running wpForo Forum. Because time-based SQL injection attacks make many requests with deliberate delays, a hit is often followed by a burst of similar requests — check the server's access log for repeated requests to forum pages with wpfob= values containing parentheses, SQL keywords, or comment characters. Confirm whether the targeted site runs wpForo Forum ≤ 2.4.14; if so, update to 2.4.15 or later immediately as the definitive fix. If exploitation cannot be ruled out, treat the entire WordPress database as potentially read by the attacker: rotate the WordPress admin password, any service account credentials stored in the database, and any API keys configured in the site's settings. Also consider that successful database read can expose session tokens that may allow the attacker to log in as any user without needing to crack a password hash.