# CVE-2018-21007: Path traversal in n/a

> An attacker can directly access sensitive Excel files in the uploads directory due to missing access controls in the WooCommerce Confirmation Email plugin.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3jc7-fxmm-792m

## What is CVE-2018-21007?

CVE-2018-21007 is a critical path traversal vulnerability in n/a, published on 29 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The woo-confirmation-email plugin before 3.2.0 for WordPress has no blocking of direct access to supportive xl folders inside uploads.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2018-21007?

It affects 1 product.


Products: Wisetr User Email Verification for Woocommerce.

## How do I fix CVE-2018-21007?

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

## Is CVE-2018-21007 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-2781](https://insights.sbomify.com/CVE-2023-2781/): User Email Verification for WooCommerce <= 3.5.0 - Authentication Bypass (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-21007 and fix it if it is affected.

What it is: CVE-2018-21007 is a critical path traversal vulnerability in n/a, published on 29 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-21007 in the wild and no public exploit code.

Affected product: n/a. 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-2018-21007/ (Markdown: https://insights.sbomify.com/CVE-2018-21007/index.md)
```

## Sources

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

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