CVE-2026-28562: gVectors Team wpForo Forum · SQL Injection
Affects gVectors Team wpForo ForumSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 2.4.15 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.4.15
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade gVectors Team wpForo Forum to 2.4.15.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| gVectors TeamwpForo Forum | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, users should consider disabling or restricting access to the vulnerable wpForo Forum 2.4.14 component or applying custom input validation and filtering on the wpfob parameter to mitigate exploitation risk.
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.