dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-12110

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 'task_search' 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. The wppm_get_task_list AJAX handler performs no capability check and no nonce verification, meaning any authenticated user including those with Subscriber-level access can invoke it directly.

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.8 contain a SQL injection vulnerability in the wppm_get_task_list AJAX handler. The 'task_search' parameter is insufficiently escaped and the existing SQL query lacks prepared statement usage, allowing authenticated attackers with subscriber-level access to inject arbitrary SQL queries and extract sensitive database information.

MitigationUpdate the Taskbuilder plugin to a version beyond 5.0.8 that implements proper SQL escaping using $wpdb->prepare(), adds capability checks, and includes nonce verification for the AJAX handler.

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 below the plugin name.
    Affected if Taskbuilder plugin is not installed or cannot be found in the plugins list
  2. Confirm installed version number
    Check the version displayed next to the Taskbuilder plugin name in the WordPress plugins page. Compare it to the affected range: versions 5.0.8 and below are vulnerable.
    Affected if The installed version is 5.0.8 or lower
  3. Identify the vulnerable AJAX endpoint
    Inspect the plugin files for the wppm_get_task_list AJAX handler. This is typically registered via add_action('wp_ajax_wppm_get_task_list', ...) or wp_ajax_nopriv_wppm_get_task_list in the plugin PHP files.
    Affected if The wppm_get_task_list AJAX action is registered in the plugin
  4. Verify subscriber-level access to the handler
    Check if the AJAX handler allows access to subscriber-level users. Look for missing capability checks or capability checks that allow 'read' or 'subscriber' roles in the wppm_get_task_list callback function.
    Affected if The AJAX handler is accessible to users with subscriber-level permissions without proper capability checks
  5. Check for unescaped task_search parameter usage
    Review the wppm_get_task_list handler code to see if the task_search POST/GET parameter is used directly in SQL queries without $wpdb->prepare() or proper escaping using esc_sql().
    Affected if The task_search parameter is used in SQL queries without prepare() or esc_sql() escaping

If the Taskbuilder plugin version is 5.0.8 or lower and the wppm_get_task_list AJAX handler is accessible to subscriber-level users, the environment is affected by this SQL injection vulnerability.

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 a version beyond 5.0.8 that implements proper SQL escaping using $wpdb->prepare(), adds capability checks, and includes nonce verification for the AJAX handler.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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