# CVE-2026-9570: Taskbuilder < 5.0.8 - Reflected XSS via Shortcode

> Attackers can execute arbitrary JavaScript in the context of logged-in users via a reflected XSS vulnerability in the Taskbuilder WordPress plugin.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jun 2026
- **Updated:** 17 Jun 2026
- **Also known as:** GHSA-jf67-82h5-mx67

## What is CVE-2026-9570?

CVE-2026-9570 is a high-severity cross-site scripting vulnerability in Unknown Taskbuilder, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-9570?


## How do I fix CVE-2026-9570?

No fix has been published for CVE-2026-9570 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9570 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9570 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9570 and fix it if it is affected.

What it is: CVE-2026-9570 is a high-severity cross-site scripting vulnerability in Unknown Taskbuilder, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9570 exists.

Affected product: Unknown Taskbuilder. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9570/ (Markdown: https://insights.sbomify.com/CVE-2026-9570/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9570
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9570
- OSV: https://osv.dev/vulnerability/CVE-2026-9570

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9570/
Summaries are generated and may contain mistakes; the official description above is the record.