# CVE-2024-11396: Event monster <= 1.4.3 - Information Exposure Via Visitors List Export

> Unauthenticated attackers can access exported visitor data via a publicly accessible CSV file with a hardcoded filename.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 13 Jan 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-6x4w-fvqp-6jvc

## What is CVE-2024-11396?

CVE-2024-11396 is a medium-severity vulnerability in awordpresslife Event Monster – Manager & Ticket Booking, published on 13 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Event Monster – Event Management, Tickets Booking, Upcoming Event plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.4.3 via the Visitors List Export file. During the export, a CSV file is created in the wp-content folder with a hardcoded filename that is publicly accessible. This makes it possible for unauthenticated attackers to extract data about event visitors, that includes first and last names, email, and phone number.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Awplife Event Monster.

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

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

## Is CVE-2024-11396 being exploited?

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

Public exploit code:

- Event monster <= 1.4.3 - Information Exposure Via Visitors List Export (github_poc): https://github.com/RandomRobbieBF/CVE-2024-11396
- Event Monster <= 1.4.3 - Information Exposure Via Visitors List Export (nuclei): http/cves/2024/CVE-2024-11396.yaml

## Other vulnerabilities in awordpresslife Event Monster – Manager & Ticket Booking

- [CVE-2024-1895](https://insights.sbomify.com/CVE-2024-1895/): Event Monster <= 1.3.9 - Authenticated(Contributor+) PHP Object Injection via Custom Meta (high 7.5)
- [CVE-2022-3720](https://insights.sbomify.com/CVE-2022-3720/): Event Monster < 1.2.1 - Admin+ SQLi (high 7.2)
- [CVE-2023-47525](https://insights.sbomify.com/CVE-2023-47525/): WordPress Event Management Tickets Booking Plugin <= 1.3.2 is vulnerable to Cross Site Scripting (XSS) (medium 5.9)
- [CVE-2024-5059](https://insights.sbomify.com/CVE-2024-5059/): WordPress Event Monster Plugin <= 1.4.0 - Sensitive Data Exposure vulnerability (medium 5.3)
- [CVE-2022-3336](https://insights.sbomify.com/CVE-2022-3336/): Event Monster < 1.2.0 - Visitors Deletion via CSRF (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-11396 is a medium-severity vulnerability in awordpresslife Event Monster – Manager & Ticket Booking, published on 13 Jan 2025. 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-11396 exists.

Affected product: awordpresslife Event Monster – Manager & Ticket Booking. 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-11396/ (Markdown: https://insights.sbomify.com/CVE-2024-11396/index.md)
```

## Sources

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

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