dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-1639

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Taskbuilder – WordPress Project Management & Task Management plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'order' and 'sort_by' parameters in all versions up to, and including, 5.0.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, 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 Taskbuilder WordPress plugin versions up to 5.0.2 contain a time-based blind SQL injection vulnerability in the 'order' and 'sort_by' parameters. Authenticated attackers with subscriber-level access can exploit insufficient input sanitization and lack of prepared statements to inject malicious SQL queries and extract sensitive database information.

MitigationUpdate the Taskbuilder plugin to version 5.0.3 or later, which contains the patched code with proper input escaping and prepared SQL statements.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Taskbuilder plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Taskbuilder' in the installed plugins list, or check the /wp-content/plugins/ directory for the taskbuilder folder
    Affected if Taskbuilder plugin is present in the WordPress installation
  2. Check installed Taskbuilder version
    In WordPress admin > Plugins, find Taskbuilder and view the version number displayed under the plugin name, or inspect the main plugin file header in /wp-content/plugins/taskbuilder/
    Affected if Version is 5.0.2 or lower (any version up to and including 5.0.2)
  3. Verify subscriber-level user accounts exist
    In WordPress admin > Users, review the user list and their assigned roles. Check if any users have the 'Subscriber' role assigned
    Affected if At least one user with Subscriber role exists in the WordPress site
  4. Confirm plugin endpoint accessibility
    Inspect the Taskbuilder plugin code to identify AJAX endpoints or form handlers that process the 'order' and 'sort_by' parameters. These are typically found in PHP files handling task or project listing functionality
    Affected if The plugin processes user-supplied 'order' or 'sort_by' parameters without prepared statements

A user is affected if Taskbuilder plugin version 5.0.2 or lower is installed AND the site has subscriber-level users who can access the vulnerable order/sort_by parameters.

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

Update the Taskbuilder plugin to version 5.0.3 or later, which contains the patched code with proper input escaping and prepared SQL statements.

Recommended fix Moderate confidence

Taskbuilder plugin version 5.0.3

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Taskbuilder – WordPress Project Management & Task Management plugin
  4. Check if current version is below 5.0.3
  5. If vulnerable, click 'Update Now' to upgrade to version 5.0.3 or latest available version
  6. After update, verify the plugin version has changed to 5.0.3 or higher
  7. Test that the plugin functionality works correctly after the update

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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