dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-9570

HIGH · 7.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 plugin before 5.0.8 does not properly sanitise a URL parameter before echoing it into inline JavaScript on a frontend page containing one of its shortcodes, leading to a Reflected Cross-Site Scripting vulnerability that can be triggered against any logged-in user.

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 before version 5.0.8 contains a reflected Cross-Site Scripting (XSS) vulnerability. The plugin fails to properly sanitize a URL parameter before echoing it into inline JavaScript on frontend pages containing its shortcodes. This allows an attacker to inject malicious JavaScript that executes in the context of any logged-in user's browser session.

MitigationUpdate the Taskbuilder plugin to version 5.0.8 or later, which includes proper sanitization of URL parameters before they are echoed into inline JavaScript.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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
    Log in to WordPress admin, go to Plugins > Installed Plugins, and look for 'Taskbuilder' in the list. Alternatively, check if the /wp-content/plugins/taskbuilder/ directory exists on the server.
    Affected if Taskbuilder plugin is present in the WordPress installation
  2. Check installed version against vulnerable range
    In WordPress admin, click on the Taskbuilder plugin to view its version number. Compare this to version 5.0.8. The vulnerability affects versions before 5.0.8.
    Affected if Installed version is lower than 5.0.8 (e.g., 5.0.7, 5.0.6, etc.)
  3. Identify pages using Taskbuilder shortcodes
    Search the WordPress database or content for the Taskbuilder shortcode (commonly [taskbuilder] or similar). Use WP admin > Pages/Posts and search for the shortcode, or inspect page content files in the database.
    Affected if Any published page or post contains the Taskbuilder shortcode and is accessible to logged-in users
  4. Check for vulnerable URL parameter handling
    Visit a page containing the Taskbuilder shortcode and examine the page source for inline JavaScript that reflects URL parameters. Look for unsanitized echo of request parameters (e.g., $_GET values) in script tags.
    Affected if Inline JavaScript on shortcode pages reflects URL parameters without proper escaping or sanitization

A user is affected if the Taskbuilder plugin is installed with a version lower than 5.0.8 AND any frontend page contains the plugin shortcode that could reflect URL parameters into inline JavaScript.

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.8 or later, which includes proper sanitization of URL parameters before they are echoed into inline JavaScript.

Recommended fix High confidence

5.0.8

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins page.
  3. 3. Locate the Taskbuilder plugin in the installed plugins list.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 5.0.8.
  5. 5. Alternatively, manually update by downloading version 5.0.8 from the WordPress plugin repository or the vendor.
  6. 6. After updating, verify the plugin version shows 5.0.8 in the Plugins list.
  7. 7. Test the affected shortcode functionality to ensure the update did not break existing features.
Caveat Minor plugin version upgrades typically do not introduce breaking changes, but test critical workflows after updating

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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