# CVE-2024-38735: WordPress Event post plugin <= 5.9.5 - Local File Inclusion vulnerability

> Attackers can exploit a local file inclusion flaw in the Event post plugin to read sensitive files or execute arbitrary code.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jul 2024
- **Updated:** 11 May 2026
- **Also known as:** GHSA-qgc6-gm7v-g299

## What is CVE-2024-38735?

CVE-2024-38735 is a high-severity path traversal vulnerability in Bastien Ho Event post, published on 12 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Bastien Ho Event post event-post.This issue affects Event post: from n/a through <= 5.9.5.

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

## Which versions are affected by CVE-2024-38735?


## How do I fix CVE-2024-38735?

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

## Is CVE-2024-38735 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-38735 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-38735 and fix it if it is affected.

What it is: CVE-2024-38735 is a high-severity path traversal vulnerability in Bastien Ho Event post, published on 12 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-38735 exists.

Affected product: Bastien Ho Event post. 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-2024-38735/ (Markdown: https://insights.sbomify.com/CVE-2024-38735/index.md)
```

## Sources

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

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