dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-1581

HIGH · 7.5 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
The wpForo Forum plugin for WordPress is vulnerable to time-based SQL Injection via the 'wpfob' parameter in all versions up to, and including, 2.4.14 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the 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

The wpForo Forum plugin for WordPress versions up to 2.4.14 contains an unauthenticated time-based SQL injection vulnerability via the 'wpfob' parameter. The root cause is insufficient input sanitization combined with the absence of prepared statements in the SQL query, allowing attackers to inject arbitrary SQL commands to extract sensitive database information.

MitigationUpgrade to wpForo Forum plugin version 2.4.15 or later which contains the security fix. Until the patch is applied, consider disabling the plugin or implementing WAF rules to block SQL injection attempts targeting the 'wpfob' parameter.

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

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
None
Availability
None

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

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. Confirm wpForo plugin installation and version
    Check the wp-content/plugins/wpforo folder for the main plugin file (usually wpforo.php) and read the Version header from the plugin comments, or access it via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin is installed and the version listed is 2.4.14 or lower
  2. Verify the vulnerable parameter endpoint is reachable
    Identify URLs on your site that may accept the 'wpfob' parameter, typically in frontend forum pages or shortcode-rendered content; test with a benign request to confirm the parameter is processed
    Affected if The 'wpfob' parameter is accepted and processed by the site without authentication
  3. Confirm the SQL injection condition exists
    Send a time-based SQL injection test payload via the 'wpfob' parameter (e.g., adding SLEEP(5) to the parameter value) and observe if the response delays by approximately 5 seconds or more
    Affected if The response time increases significantly, indicating the SQL injection vulnerability is present and exploitable

You are affected if the wpForo plugin version is 2.4.14 or lower AND the 'wpfob' parameter endpoint is accessible and responds to SQL injection testing with delayed responses.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to wpForo Forum plugin version 2.4.15 or later which contains the security fix. Until the patch is applied, consider disabling the plugin or implementing WAF rules to block SQL injection attempts targeting the 'wpfob' parameter.

Recommended fix Moderate confidence

wpForo Forum version 2.4.15 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the wpForo Forum plugin
  4. Check the current version installed (should be 2.4.14 or below if vulnerable)
  5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. Alternatively, download version 2.4.15 or later from the WordPress plugin repository and upload manually via Plugins > Add New > Upload Plugin
  7. After updating, verify the plugin version shows 2.4.15 or higher
  8. Consider running a database security scan to confirm the vulnerability is no longer exploitable

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1581 — 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-1581 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