# CVE-2026-49779: WordPress Tax Exempt for WooCommerce plugin < 1.9.5 - Path Traversal vulnerability

> An attacker can exploit a path traversal vulnerability in the Tax Exempt for WooCommerce plugin to read arbitrary files on the server.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-3wjp-774c-xvqr

## What is CVE-2026-49779?

CVE-2026-49779 is a medium-severity path traversal vulnerability in Addify Tax Exempt for WooCommerce, published on 2 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Path Traversal: '.../...//' vulnerability in Addify Tax Exempt for WooCommerce allows Path Traversal.

This issue affects Tax Exempt for WooCommerce: from n/a before 1.9.5.

Weakness: CWE-35 (Path Traversal: '.../...//')

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


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

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

## Is CVE-2026-49779 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-49779 is a medium-severity path traversal vulnerability in Addify Tax Exempt for WooCommerce, published on 2 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49779 in the wild and no public exploit code.

Affected product: Addify Tax Exempt for WooCommerce. 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-49779/ (Markdown: https://insights.sbomify.com/CVE-2026-49779/index.md)
```

## Sources

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

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