CVE-2026-28562 Details
Description
wpForo 2.4.14 contains an unauthenticated SQL injection vulnerability in Topics::get_topics() where the ORDER BY clause relies on ineffective esc_sql() sanitization on unquoted identifiers. Attackers exploit the wpfob parameter with CASE WHEN payloads to perform blind boolean extraction of credentials from the WordPress database.
A SQL injection vulnerability has been identified in the wpForo WordPress plugin, specifically in version 2.4.14. The issue arises in the Topics::get_topics() function, where the ORDER BY clause is vulnerable to injection attacks. This vulnerability is due to inadequate sanitization of unquoted identifiers, allowing attackers to exploit the wpfob parameter with CASE WHEN payloads. This exploitation enables blind boolean extraction of credentials from the WordPress database.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Mar 2, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://wordpress.org/plugins/wpforo/ | [email protected] | Product |
| https://wordpress.org/plugins/wpforo/#developers | [email protected] | Release Notes |
| https://www.vulncheck.com/advisories/wpforo-sql-injection-via-topics-order-by-parameter | [email protected] | Third Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-89 | Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| gvectors wpforo forum | >= 2.4.0, < 2.4.15 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Mar 5, 2026 | Initial Analysis | [email protected] |
| Feb 28, 2026 | New CVE Received | [email protected] |