CVE-2026-28562
Unauthenticated SQL Injection in wpForo 2.4.14 Enables Data Theft
Publication date: 2026-02-28
Last updated on: 2026-03-05
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gvectors | wpforo_forum | From 2.4.0 (inc) to 2.4.15 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in wpForo 2.4.14 is an unauthenticated SQL injection found in the Topics::get_topics() function. It occurs because the ORDER BY clause uses ineffective sanitization (esc_sql()) on unquoted identifiers. Attackers can exploit the wpfob parameter by injecting CASE WHEN payloads, allowing them to perform blind boolean extraction of credentials from the WordPress database.
How can this vulnerability impact me? :
This vulnerability can have a severe impact as it allows attackers to extract sensitive credentials from the WordPress database without authentication. This can lead to unauthorized access to user data, potential account compromise, and further exploitation of the affected system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know