dbcve.org
Wpforo ForumWordPress extension · Gvectors

CVE-2026-28562

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-28
Fix available
A fix is available. Upgrade to 2.4.15 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

wpForo 2.4.14 has an unauthenticated SQL injection in Topics::get_topics() where the ORDER BY clause uses esc_sql() on unquoted identifiers (column names), which fails to prevent injection. Attackers exploit the wpfob parameter with CASE WHEN payloads to perform blind boolean-based extraction of WordPress database credentials.

MitigationApply any available wpForo security update immediately; if no patch exists, consider temporarily disabling the plugin or deploying WAF rules to block SQL injection patterns in the wpfob parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wpforo ForumWordPress extension
Affected:>= 2.4.0, < 2.4.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify wpForo installation and version
    Check the plugin header in wp-content/plugins/wpforo/wpforo.php or view the installed plugins list in WordPress admin under Plugins > Installed Plugins. Look for the Version field.
    Affected if The installed version is 2.4.0 through 2.4.14 (inclusive)
  2. Confirm Topics::get_topics() is accessible
    Locate the file wp-content/plugins/wpforo/includes/classes/topics.php and verify the get_topics() method exists. This method handles the wpfob parameter for ordering forum topics.
    Affected if The file exists and contains the vulnerable method using esc_sql() on the wpfob parameter
  3. Verify the wpfob parameter is processed without proper quoting
    Search the topics.php file for code handling the ORDER BY clause with the wpfob parameter. Look for code where esc_sql() is applied to $wpfob without surrounding the value in backticks or validating against an allowed column list.
    Affected if esc_sql() is called on the wpfob parameter directly without backtick quoting or whitelist validation
  4. Confirm unauthenticated access to the vulnerable endpoint
    Test access to the forum topics page (typically /community/ or /forum/ slug) without logging in. The vulnerability is unauthenticated, so no login should be required to send the wpfob parameter.
    Affected if The forum topics page is publicly accessible and accepts the wpfob parameter in GET or POST requests

You are affected if wpForo version is 2.4.0 through 2.4.14 and the forum topics page is publicly accessible, allowing unauthenticated injection through the wpfob parameter in the ORDER BY clause.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.15 or later
Fixed in 2.4.15
Interim mitigation

Apply any available wpForo security update immediately; if no patch exists, consider temporarily disabling the plugin or deploying WAF rules to block SQL injection patterns in the wpfob parameter.

Recommended fix High confidence

wpForo 2.4.15 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate wpForo Forum in the plugin list
  4. Check the current version number to confirm it is between 2.4.0 and 2.4.14 inclusive
  5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. Alternatively, download wpForo Forum version 2.4.15 or later from wordpress.org/plugins/wpforo/
  7. Deactivate the current plugin, delete it, then upload and install the new version
  8. Activate the updated plugin
Caveat Review wpForo release notes before upgrading as minor plugin updates may introduce configuration or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wpforo Forum Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28562 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28562 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data