OceanWP stored XSS in EDD download category names
- Exploited
- No known exploitation
- Fix
- Fixed in 4.2.9
- Who is exposed
- Not reported
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
Original 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
Upgrade to a fixed version: 4.2.9.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Affected versions
- oceanwp oceanwpfixed in 4.2.9
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.8/10CVSS 4.8
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134136 |
| Other links 3 | |
| Patch | GitHub · oceanwp/oceanwp · Release 4.2.9 |
| Report | GitHub · oceanwp/oceanwp · Pull request #577 |
| Link | vulncheck.com · advisories/oceanwp-before-stored-xss-via-edd-category-name |
Questions about CVE-2026-134136
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: cve.now feed data
Which versions are affected by CVE-2026-134136?
oceanwp: before 4.2.9.
Source: cve.now feed data
How do I fix CVE-2026-134136?
Upgrade to a fixed version: 4.2.9.
Source: cve.now feed data
Related
- CVE-2023-23700WordPress OceanWP theme <= 3.4.1 - Authenticated Local File Inclusion vulnerability
- CVE-2026-81929Ocean Pro Demos <= 1.5.4 and Ocean eComm Treasure Box <= 1.8.0 - Unauthenticated Stored Cross-Site Scripting via 'content' Parameter
- CVE-2026-115592WordPress OceanWP theme <= 4.2.7 - Cross Site Scripting (XSS) vulnerability
- CVE-2026-86803Ocean Extra <= 2.6.0 - Unauthenticated Arbitrary Shortcode Execution via 'oceanwp_library' Shortcode Template
- CVE-2025-49068WordPress Ocean Extra plugin <= 2.4.8 - Cross Site Scripting (XSS) vulnerability
- CVE-2025-3472Ocean Extra <= 2.4.6 - Unauthenticated Arbitrary Shortcode Execution
No corrections so far. Something wrong on this page? Report an error.