# CVE-2026-84898: Eventin < 4.1.21 - Contributor+ LFI via Event Layout Meta

> Contributors can exploit a path traversal flaw in the Eventin WordPress plugin to include and execute arbitrary local PHP files.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/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:** 5 Sep 2026
- **Updated:** 6 Sep 2026
- **Also known as:** GHSA-jr8r-6xgg-xqr4

## What is CVE-2026-84898?

CVE-2026-84898 is a medium-severity path traversal vulnerability in Unknown Eventin, published on 5 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Eventin  WordPress plugin before 4.1.21 does not properly validate a template path value before using it to include a local file, allowing users with contributor-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-84898?


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

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

## Is CVE-2026-84898 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84898 is a medium-severity path traversal vulnerability in Unknown Eventin, published on 5 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-84898 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-84898/ (Markdown: https://insights.sbomify.com/CVE-2026-84898/index.md)
```

## Sources

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

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