# CVE-2026-96824: WordPress Template Kit – Import plugin <= 1.0.16 - Arbitrary File Deletion vulnerability

> An attacker with editor privileges can delete arbitrary files on the server via path traversal in the Template Kit Import plugin.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-644x-4fmf-9779

## What is CVE-2026-96824?

CVE-2026-96824 is a medium-severity path traversal vulnerability in envato Template Kit – Import, published on 30 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Editor Arbitrary File Deletion in Template Kit – Import <= 1.0.16 versions.

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

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


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

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

## Is CVE-2026-96824 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96824 is a medium-severity path traversal vulnerability in envato Template Kit – Import, published on 30 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-96824 in the wild and no public exploit code.

Affected product: envato Template Kit – Import. 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-96824/ (Markdown: https://insights.sbomify.com/CVE-2026-96824/index.md)
```

## Sources

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

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