# CVE-2026-75963: Events Made Easy <= 3.2.5 - Authenticated (Contributor+) Local File Inclusion via 'wp_page_template' Event Property

> Authenticated contributors can exploit a local file inclusion vulnerability in the Events Made Easy plugin to execute arbitrary PHP code or read sensitive data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 20 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-72g6-93fc-8m5w

## What is CVE-2026-75963?

CVE-2026-75963 is a high-severity path traversal vulnerability in liedekef Events Made Easy, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Events Made Easy plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.2.5 via the eme_single_event_page_template function. This makes it possible for authenticated attackers, with contributor-level access and above, to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. The stored traversal payload is triggered passively when any visitor loads the affected single-event page, meaning post-submission execution does not require additional attacker interaction.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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


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

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

## Is CVE-2026-75963 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75963 is a high-severity path traversal vulnerability in liedekef Events Made Easy, published on 20 Aug 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-75963 in the wild and no public exploit code.

Affected product: liedekef Events Made Easy. 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-75963/ (Markdown: https://insights.sbomify.com/CVE-2026-75963/index.md)
```

## Sources

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

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