dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-6225

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-14
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 – Project Management & Task Management Tool With Kanban Board plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'project_search' parameter in all versions up to, and including, 5.0.6 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 is vulnerable to time-based blind SQL injection via the 'project_search' parameter in versions up to 5.0.6. Insufficient input sanitization and lack of prepared statements in the SQL query allow authenticated attackers with Subscriber-level access to inject malicious SQL queries and extract sensitive data from the database.

MitigationUpdate the Taskbuilder plugin to version 5.0.7 or later which contains the security fix. Until then, limit user registration to trusted personnel only and monitor for anomalous SQL patterns in requests.

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
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Taskbuilder' in the list. Note the version number displayed alongside the plugin name.
    Affected if Taskbuilder plugin is present and the version shown is 5.0.6 or lower
  2. Confirm the vulnerable parameter exists
    The plugin must have functionality that accepts a 'project_search' parameter. This is typically used in project listing or search features within the plugin frontend or backend.
    Affected if The plugin has a project search feature that processes user input through the 'project_search' parameter
  3. Check if user registration is enabled
    In WordPress admin, go to Settings > General and verify if 'Anyone can register' is checked, and what the default user role is set to.
    Affected if User registration is enabled and the default role includes Subscriber-level access, allowing untrusted users to authenticate
  4. Identify exposed endpoints
    Review the plugin's available URLs or AJAX actions that accept the project_search parameter. These are typically accessible to any authenticated user with Subscriber role or higher.
    Affected if Endpoints accepting project_search input are accessible to low-privileged authenticated users

You are affected if the Taskbuilder plugin version is 5.0.6 or lower AND the project_search parameter is accessible to Subscriber-level users in your environment.

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.7 or later which contains the security fix. Until then, limit user registration to trusted personnel only and monitor for anomalous SQL patterns in requests.

Recommended fix High confidence

5.0.7

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the Taskbuilder – Project Management & Task Management Tool With Kanban Board plugin
  4. Click 'Update now' if an update is available, or manually update to version 5.0.7 or later

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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