dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-12090

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-01
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 7 weeks old

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 generic SQL Injection via the 'wppm_proj_filter' parameter in all versions up to, and including, 5.0.8 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. No nonce verification is performed on the wp_ajax_wppm_view_project_tasks handler, meaning any authenticated session — including subscriber-level — can reach the vulnerable code path without any additional preconditions.

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

SQL Injection vulnerability in the Taskbuilder WordPress plugin allows authenticated users with subscriber-level access to inject malicious SQL queries via the 'wppm_proj_filter' parameter in the wp_ajax_wppm_view_project_tasks handler due to insufficient input sanitization and lack of prepared statements.

MitigationUpdate the Taskbuilder plugin to version 5.0.9 or later which includes proper input sanitization and prepared SQL statements. If immediate patching is not feasible, disable the wp_ajax_wppm_view_project_tasks ajax handler until the fix can be applied.

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 dashboard > Plugins and confirm the Taskbuilder plugin appears in the installed plugins list, or query the database wp_options table for option_name 'active_plugins'
    Affected if Taskbuilder plugin is present and active in WordPress
  2. Retrieve the installed Taskbuilder version
    Access WordPress admin > Plugins > Taskbuilder and read the version number displayed, or inspect the plugin main file header for 'Version:' tag, or query wp_options for 'taskbuilder_version' or similar version option
    Affected if Version is lower than 5.0.9 (the patched release)
  3. Confirm the vulnerable AJAX handler exists
    Inspect the Taskbuilder plugin files for 'wp_ajax_wppm_view_project_tasks' function definition, typically in the main plugin file or an ajax-handler.php file
    Affected if The wp_ajax_wppm_view_project_tasks handler is present in the plugin code
  4. Verify subscriber-level access to the endpoint
    Check WordPress user roles and confirm subscribers can make AJAX requests to /wp-admin/admin-ajax.php?action=wppm_view_project_tasks, or inspect the add_action('wp_ajax_wppm_view_project_tasks') call for privilege checks
    Affected if No capability check or role verification is enforced before processing the wppm_proj_filter parameter
  5. Test for lack of prepared statements in the SQL query
    Review the wppm_view_project_tasks handler source code and locate the database query using the wppm_proj_filter parameter; confirm it uses direct string concatenation rather than $wpdb->prepare() or parameterized queries
    Affected if The wppm_proj_filter parameter is used directly in SQL without sanitization or prepared statements

A user is affected if the Taskbuilder plugin is installed with a version below 5.0.9 and the wp_ajax_wppm_view_project_tasks AJAX handler is accessible to subscriber-level users without proper input sanitization or prepared statements in the query logic.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Taskbuilder plugin to version 5.0.9 or later which includes proper input sanitization and prepared SQL statements. If immediate patching is not feasible, disable the wp_ajax_wppm_view_project_tasks ajax handler until the fix can be applied.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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