# CVE-2026-73383: WordPress CTX Feed plugin <= 6.6.47 - Arbitrary File Download vulnerability

> An attacker with shop manager privileges can download arbitrary files from the server due to a path traversal vulnerability in the CTX Feed plugin.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-qr66-8jmv-phv2

## What is CVE-2026-73383?

CVE-2026-73383 is a medium-severity path traversal vulnerability in WebAppick CTX Feed, published on 18 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Shop manager Arbitrary File Download in CTX Feed <= 6.6.47 versions.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-73383 being exploited?

There is no known exploitation of CVE-2026-73383 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73383 is a medium-severity path traversal vulnerability in WebAppick CTX Feed, published on 18 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73383 in the wild and no public exploit code.

Affected product: WebAppick CTX Feed. 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-73383/ (Markdown: https://insights.sbomify.com/CVE-2026-73383/index.md)
```

## Sources

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

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