# CVE-2026-13170: Eventin < 4.1.20 - Editor+ Local File Inclusion via speaker_template Setting

> Editors can exploit a local file inclusion vulnerability in the Eventin WordPress plugin to execute arbitrary PHP code.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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:** 10 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-gchq-rq43-fjjm

## What is CVE-2026-13170?

CVE-2026-13170 is a high-severity path traversal vulnerability in Unknown Eventin, published on 10 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Eventin  WordPress plugin before 4.1.20 does not properly validate a template path setting before using it to include a local file, allowing users with editor-level access and above to include and execute arbitrary local PHP files.

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

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


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

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

## Is CVE-2026-13170 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13170 is a high-severity path traversal vulnerability in Unknown Eventin, published on 10 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-13170 in the wild and no public exploit code.

Affected product: Unknown Eventin. 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-13170/ (Markdown: https://insights.sbomify.com/CVE-2026-13170/index.md)
```

## Sources

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

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